Visual editor for electronic mail

ABSTRACT

A visual editor for generating a custom email message. An editor interface may display an approximation of an email message. A user may customize content and layout of an email message through the editor interface. A user interface system may track such customizations to enable faster remote operations to be performed on content of the email message. A plurality of substantially modular renderers may enable a plurality of different output representations to be generated from a single stored representation of the email message.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims the benefit under 35U.S.C. §120 of U.S. application Ser. No. 11/655,731, entitled “VISUALEDITOR FOR ELECTRONIC MAIL,” filed on Jan. 19, 2007, which is herebyincorporated herein by reference in its entirety.

BACKGROUND

1. Field of Invention

The instant invention relates to designing electronic mail (email)messages, and, more particularly, the instant invention relates to theediting of content and layout of email messages.

2. Discussion of Related Art

One way organizations have typically provided information, such asadvertisements, coupons, news, etc., to customers, members, and/or thepublic in general is through mass distributions of mail. The Internetallows distribution of information to be performed cheaper and quickerthrough email rather than traditional mail. Using email, an organizationcan generate an email message containing, for example, an advertisementor a newsletter and nearly instantly send the email to recipients aroundthe world.

Despite the cost reduction in distributing information by sending emailrather than traditional mail, organizations, such as corporations,non-profit groups, and community or religious organizations, can stillspend large amounts of money and time to prepare and transmit aneffective email campaign to a large number of recipients. For example,organizations may hire designers to design email layouts, graphics,text, and advertising elements individualized for each email campaign.Organizations may also purchase computer systems to generate andtransmit the email and hire technology experts to upkeep these computersystems.

To ease the creation of effective email campaigns, email design toolshave been developed. Such tools include wizards and templates thatprovide organizations with tools to more easily design effective emailcampaigns. Furthermore, email transmission services have been developedthat manage recipient lists and transmit email messages. Such servicesallow an organization to transmit large numbers of email messages toextensive recipient lists without the need to purchase specializedcomputer systems or hire experts to maintain such computer systems.

SUMMARY OF INVENTION

In one aspect of the instant invention, it is realized that an editorthat allows a user to visually edit the layout and content of emailmessages may ease the design of such email messages. In particular, anemail designer may easily design email messages using a visual editorthat displays an approximation of an email message through whichcustomization to content and layout of the email message may beperformed.

In another aspect of the instant invention, it is further realized thattracking customization of an email message with a user interface serverby storing information in local memory may enable fast spell-checking,previewing, and anti-spam functionality through an editor interface.Such tracking, for example, may, in some implementations, allow thesefunctions to be performed without a relatively slow database query. Sucha function may be advantageous, for instance, in an Internet-based emailediting system.

In one aspect of the instant invention, it is further realized that aplurality of substantially modular renderers may produce convenientvisual editor functionality based on a single stored representation ofan email message. In some implementations, the plurality of renderersmay generate different output representations of an email message basedon desired output characteristics.

One aspect of the instant invention includes a computer-implementedmethod for generating at least one custom email message based, at leastin part, on input from a user of a computer system, the computer systemhaving a display. In some embodiments, the method comprises acts ofpresenting, to the user in the display of the computer system, an editorinterface displaying an initial approximation of an email messagecomprising a plurality of content blocks; accepting, through the editorinterface, at least one customization of at least one of a content of atleast one of the plurality of content blocks and a layout of theplurality of content blocks; and displaying through the editor interfacea customized approximation of the email message based, at least in part,on the initial approximation of the email message and the at least onecustomization.

In some embodiments, the initial approximation includes a representationof a template document. Some embodiments further comprise an act ofreceiving an indication of the template document from the user. In someembodiments, the template document includes an extensible markuplanguage document. In some embodiments, the extensible markup languagedocument defines each of the plurality of content blocks and a pluralityof layout panels. Some embodiments further comprise an act ofdetermining at least one control element of a control panel of theeditor interface based, at least in part, on the template document. Insome embodiments, the at least one control element includes at least oneof a formatting element and a block adding interface. In someembodiments, the at least one customization includes a customization ofthe content of the at least one of the plurality of content blocks. Insome embodiments, the customization of the content includes at least oneof a customization of textual information, a customization of graphicalinformation, a customization of data-driven information, a customizationof partner information, and a customization of link information.

Some embodiments further comprise an act of saving a representation ofthe customized content of the at least one of the plurality of contentblocks to at least one database table. Some embodiments further comprisean act of presenting, through the editor interface, a block interfaceallowing the user to customize the content of the at least one of theplurality of content blocks. In some embodiments, the block interfaceincludes a hypertext markup language Iframe. In some embodiments,presenting the block interface includes displaying the hypertext markuplanguage Iframe over the at least one of the plurality of contentblocks. In some embodiments, presenting the block interface includesconverting at least one cascading style sheet style class to at leastone inline hypertext markup language style tag.

In some embodiments, the at least one customization includes acustomization of the layout of the plurality of content blocks. In someembodiments, the customization of the layout includes a movement of atleast one of the plurality of content blocks from an initial position toa desired position. In some embodiments, the customization of the layoutincludes at least one of an addition of a new content block to theplurality of content blocks and a deletion of one of the plurality ofcontent blocks. Some embodiments further comprise an act of saving arepresentation of the content of the at least one of the plurality ofcontent blocks in local memory of at least one user interface server.

Some embodiments further comprise an act of presenting, through theeditor interface, at least one intermediate representation of thecustomization of the layout. In some embodiments, the at least oneintermediate representation includes a representation of a movement ofthe at least one of the plurality of content blocks from an initialposition to a desired position. In some embodiments, the at least oneintermediate representation includes an indication of a location atwhich a new content block may be added. Some embodiments furthercomprise an act of generating the initial approximation. In someembodiments, generating the initial approximation comprises generatingthe initial approximation based, at least in part, on a representationof a document object model. In some embodiments, generating the initialapproximation comprises inserting at least one JavaScript hook into arepresentation of a hypertext markup language document.

In some embodiments, the editor interface includes a webpage. In someembodiments, the webpage includes an AJAX based webpage. Someembodiments further comprise an act of generating the customizedapproximation. In some embodiments, generating the customizedapproximation includes updating at least one document object modelbased, at least in part, on the at least one customization. Someembodiments further comprise an act of accepting, through the editorinterface, a global format change. Some embodiments further comprise anact of applying the global format change to the email message. In someembodiments, applying the global format change includes changing atleast one attribute of at least one cascading style sheet class based,at least in part, on the global format change. In some embodiments, theglobal format change includes at least one of a textual change and agraphical change.

In some embodiments, accepting the at least one customization includesaccepting the at least one customization through the editor interfacewhile displaying at least a portion of the initial approximation. Someembodiments further comprise an act of inserting a pre-authored contentblock into the email message. Some embodiments further comprise acts ofaccepting, through the editor interface, at least one indication of anundo request for the at least one customization; and displaying throughthe editor interface the initial approximation of the email message.Some embodiments further comprise acts of accepting, through the editorinterface, at least one indication of a redo request for the at leastone customization; and displaying through the editor interface thecustomized approximation of the email message. Some embodiments furthercomprise acts of accepting, through the editor interface, at least oneindication of a request to performing at least one of a spell check, ananti-spam check, and an insertion of data-driven content; and performingthe at least one of the spell check, the anti-spam check, and theinsertion of data driven content.

One aspect of the instant invention includes a computer-implementedmethod for generating at least one custom email message based, at leastin part, on input from a user of a computer system, the computer systemhaving a display. In some embodiments, the method comprises acts ofpresenting, to the user in the display of the computer system, an editorinterface displaying an initial approximation of an email messagecomprising a plurality of content blocks; accepting, through the editorinterface, a customization of a content of at least one of the pluralityof content blocks; accepting, through the editor interface, acustomization of a layout of the plurality of content blocks; trackingthe customization of the content and customization of the layout in amemory of a user interface server; and storing at least a representationof the customized content of the at least one of the plurality ofcontent blocks in at least one database table on a database server.

Some embodiments further comprise act of receiving an indication of asave request from the user. Some embodiments further comprise an act ofin response to the save request, storing a representation of the atleast one custom email message in the at least one database table on thedatabase server. In some embodiments, presenting the editor interfaceincludes transmitting the initial approximation of the email messagefrom the user interface server to the user. In some embodiments,tracking the customization includes storing a representation of theinitial approximation of the email message on the user interface server.In some embodiments, tracking the customization includes updating therepresentation of the initial approximation of the plurality of contentblocks stored on the user interface server based, at least in part, onthe customization of the content and the customization of the layout.

In some embodiments, accepting the customization includes receiving anindication of a save request from the user. Some embodiments furthercomprise an act of performing at least one of a spell check and ananti-spam check of at least a portion of the custom email message. Insome embodiments, performing at least one of a spell check and ananti-spam check includes performing the at least one of the spell checkand the anti-spam check using the tracked customization of the contentand customization of the layout in the memory of the user interfaceserver. In some embodiments, performing at least one of a spell checkand an anti-spam check includes performing the at least one of the spellcheck and the anti-spam check using the tracked customization of thecontent and customization of the layout in the memory of the userinterface server and without querying the database server for therepresentation of the customized content.

Some embodiments further comprise an act of displaying through theeditor interface a customized approximation of the email message based,at least in part, on the initial approximation of the email message, thecustomization of the layout, and the customization of the content. Someembodiments further comprise an act of presenting, to the user in thedisplay of the computer system, a preview representation of the customemail message. In some embodiments, the preview representation includesan approximation of the custom email message as the custom email messagemay appear to a recipient of the custom email message. In someembodiments, presenting the preview representation includes generatingthe preview representation. In some embodiments, presenting the previewrepresentation includes generating the preview representation using thetracked customization of the content and customization of the layout. Insome embodiments, presenting the preview representation includesgenerating the preview representation without querying the at least onedatabase table after presenting the editor interface.

One aspect of the instant invention includes a computer-implementedmethod for generating at least one custom email message based, at leastin part, on input from a user of a computer system, the computer systemhaving a display. In some embodiments, the method comprises acts ofreceiving from the user an indication of a desired version of the customemail message; selecting an email renderer based, at least in part, onthe indication of the desired version of the custom email message;rendering the desired version of the custom email message using theselected email renderer; and presenting, to the user in the display ofthe computer system, the desired version of the custom email message.

In some embodiments, the selected renderer includes at least one of apreview renderer, an editor renderer, and an edit text letter renderer.In some embodiments, the desired version includes a preview version andthe selected renderer includes a preview renderer. In some embodiments,rendering includes generating a hypertext markup language representationof the custom email message based, at least in part, on a documentobject model representation of the custom email message. In someembodiments, rendering includes generating a text representation of thecustom email message based, at least in part, on a document object modelrepresentation of the custom email message. In some embodiments, thepreview representation includes an approximation of the custom emailmessage as the custom email message may appear to a recipient of thecustom email message.

In some embodiments, the desired version includes a preview for at leastone of a device type, a format, and a program, and rendering includesgenerating a preview representation of the customized email messagedesigned for the at least one of the device type, the format, and theprogram based, at least in part, on a document object modelrepresentation of the custom email message. In some embodiments, thedesired version includes an editor version and the selected rendererincludes an editor renderer. In some embodiments, rendering includesgenerating a hypertext markup language representation of the customemail message based, at least in part, on a document object modelrepresentation of the custom email message. In some embodiments, theeditor version includes a plurality of JavaScript hooks that enable atleast one customization of at least one of a content of at least one ofthe plurality of content blocks and a layout of the plurality of contentblocks to be entered by the user through an editor interface.

Some embodiments further comprise an act of presenting, to the user inthe display of the computer system, the editor interface displaying theeditor version. In some embodiments, the desired version includes aneditor for a device type, and rendering includes generating an editorrepresentation of the customized email message designed for the devicetype based, at least in part, on a document object model representationof the custom email message.

In some embodiments, the desired version includes an edit text versionand the selected renderer includes an edit text renderer. In someembodiments, rendering includes generating a text representation of thecustom email message based, at least in part, on a document object modelrepresentation of the custom email message. In some embodiments, theedit text version is formatted to enable editing through an edit textinterface.

Some embodiments further comprise an act of presenting, to the user inthe display of the computer system, the edit text interface displayingthe edit text version. In some embodiments, the desired version includesan editable version for at least one of a device type, a format, and aprogram, and the selected renderer includes an edit renderer for therespective at least one of the device type, the format, and the program.In some embodiments, rendering includes generating a respective editrepresentation of the custom email message based, at least in part, on adocument object model representation of the custom email message. Insome embodiments, the respective edit version is formatted to enableediting through an edit interface. Some embodiments further comprise anact of presenting, to the user in the display of the computer system,the edit interface displaying the edit text version.

In some embodiments, the desired version includes a live version and theselected renderer includes a preview renderer. In some embodiments,rendering includes generating a hypertext markup language representationof the custom email message based, at least in part, on a documentobject model representation of the custom email message. In someembodiments, rendering includes generating a text representation of thecustom email message based, at least in part, on a document object modelrepresentation of the custom email message.

In some embodiments, rendering includes inserting at least on datadriven element into the live version. Some embodiments further comprisean act of transmitting the live version to at least one recipient.

In some embodiments, the desired version includes a live version for atleast one of a device type, a format, and a program, and renderingincludes generating a live representation of the customized emailmessage designed for the respective at least one of the device type, theformat, and the program based, at least in part, on a document objectmodel representation of the custom email message. Some embodimentsfurther comprise acts of rendering a live version of the custom emailmessage using a live renderer; and transmitting the live version to atleast one recipient. In some embodiments, rendering the live versionincludes rendering the live version for a desired device type.

In some embodiments, wherein the live renderer includes a devicespecific live renderer. In some embodiments, wherein the live rendererincludes a generic live renderer usable for a plurality of devicestypes. In some embodiments, the selected renderer includes at least oneof a device type renderer, a format type renderer, and a program typerenderer. In some embodiments, the at least one device type includes atleast one of a cellular telephone, a general purpose computer, apersonal digital assistant, a television, and a billboard. In someembodiments, the desired version respectively includes at least one of aversion designed for the device type, a version designed for the format,and a version designed for the program.

Further features and advantages of the instant invention as well as thestructure and operation of various embodiments of the instant inventionare described in detail below with reference to the accompanyingdrawings. In the drawings, like reference numerals indicate like orfunctionally similar elements. Additionally, the left-most one or twodigits of a reference numeral identifies the drawing in which thereference numeral first appears.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are not intended to be drawn to scale. In thedrawings, each identical or nearly identical component that is shown invarious figures is represented by a like numeral. For purposes ofclarity, not every component may be labeled in every drawing. In thedrawings:

FIG. 1 shows a computer system architecture that may be suitable forimplementing one or more aspects of the instant invention;

FIG. 2 shows a distributed system that may be used to perform one ormore acts in accordance with some embodiments of the instant invention;

FIG. 3 shows an example process that may be performed by an embodimentof the instant invention;

FIG. 4 shows an example template selection interface that may be used inan embodiment of the instant invention;

FIG. 5 shows an example information submission interface that may beused in an embodiment of the instant invention;

FIG. 6 shows an example editor interface that may be used in anembodiment of the instant invention;

FIG. 7 shows an example block adding interface that may be used in anembodiment of the instant invention;

FIG. 8 shows an example editor interface in which a block is being movedaccording to an embodiment of the instant invention;

FIG. 9 shows an example editor interface displaying a horizontalwrapping functionality of an embodiment of the instant invention;

FIG. 10 shows an example editor interface in which a global editingfunctionality is displayed according to an embodiment of the instantinvention;

FIG. 11 shows an editor interface in which content of a block is beingedited according to an embodiment of the instant invention;

FIG. 12 shows an example link interface according to an embodiment ofthe instant invention;

FIG. 13 shows an example image interface according to an embodiment ofthe instant invention;

FIG. 14 shows an example resize interface according to an embodiment ofthe instant invention;

FIG. 15 shows an example greeting interface according to an embodimentof the instant invention;

FIG. 16 shows an example partner integration interface according to anembodiment of the instant invention.

FIG. 17 shows an example partner integration interface according to anembodiment of the instant invention.

FIG. 18 shows an example spell check interface according to anembodiment of the instant invention;

FIG. 19 shows an example code view interface according to an embodimentof the instant invention;

FIG. 20 shows an example editor interface displaying an example specialblock according to an embodiment of the instant invention;

FIG. 21 shows an example special block editing interface according to anembodiment of the instant invention;

FIG. 22 shows an example preview representation of an email messageaccording to an embodiment of the instant invention;

FIG. 23 shows an example style sheet editing interface according to anembodiment of the instant invention;

FIG. 24 shows an example text letter editing interface according to anembodiment of the instant invention;

FIG. 25 shows an example anti-spam interface according to an embodimentof the instant invention;

FIG. 26 shows an example interface through which a user may select oneor more recipient lists according to an embodiment of the instantinvention;

FIG. 27 shows an example recipient list management interface accordingto an embodiment of the instant invention;

FIG. 28 shows an example interface that may be used in someimplementations to create a new recipient list according to anembodiment of the instant invention;

FIG. 29 shows an example entry interface according to an embodiment ofthe instant invention; and

FIG. 30 shows an example status interface according to an embodiment ofthe instant invention.

DETAILED DESCRIPTION

This invention is not limited in its application to the details ofconstruction and the arrangement of components and acts set forth in thefollowing description or shown in the drawings. The instant invention iscapable of other embodiments and of being practiced or of being carriedout in various ways. Also, the phraseology and terminology used hereinis for the purpose of description and should not be regarded aslimiting. The use of “including,” “comprising,” or “having,”“containing,” “involving,” and variations thereof herein, is meant toencompass the items listed thereafter and equivalents thereof as well asadditional items.

Some embodiments of the instant invention relate generally to a visualeditor for creating custom email messages. In some embodiments, theemail messages may be used in large scale email campaigns in which theemail messages are transmitted to a plurality of recipients identifiedin a recipient list.

In some embodiments, an editor interface is provided to a user of acomputer system through a standard web browser. In one embodiment, theeditor interface may be in the form of a program (e.g., executable,interpreted, etc.) downloaded to the user computer over a communicationnetwork such as the Internet. In some embodiments, the editor interfacemay be used to edit content and layout of an email message. In someembodiments, the editor interface may display a representation of anemail message through which the user may customize the content andlayout of the email message. By using a visual editor that allowscontent and layout customization, the user may more quickly and easilydesign custom email messages and make informed design decisions andalterations to the email message during the customization process.

In some embodiments, a user interface system may track customization ofan email message by storing information in local memory to enableoperations to be performed quickly on the email message. For example, insome implementations, spell-checking, previewing, and anti-spamfunctionality may be performed without a relatively slow database query.

In some embodiments, a plurality of substantially modular renderers(e.g., renderer processes executed by a computer system) may produceconvenient visual editor functionality based on a single storedrepresentation of an email message eliminating a need to maintainmultiple representations of a single email message. In someimplementations, the plurality of renderers may generate differentoutput representations of an email message based on desired outputcharacteristics.

General Purpose Computer System

Various aspects of the instant invention may be implemented on one ormore computer systems. These computer systems may include, for example,general-purpose computers such as those based on Intel PENTIUM-type orCore-type processor; Motorola PowerPC; AMD Athlon, Turion or Opteron;Sun UltraSPARC; Hewlett-Packard PA-RISC processors; or any other type ofprocessor. A computer system may include a single computer or may bedistributed among multiple computers attached by a communicationnetwork.

A computer system according to one embodiment may be configured toperform any of the described functions, including but not limited to,storing, transmitting, editing, formatting, tracking, retrieving,inserting information, managing information, sharing information, andcommunicating with remote systems such as image servers, billingservers, email recipients, partners, and merchants. It should beappreciated that the instant invention is not limited to having anyparticular function or set of functions.

FIG. 1 shows a block diagram of a general purpose computer and networkin which various aspects of the instant invention may be practiced. Forexample, various aspects of the instant invention may be implemented asspecialized software executing on one or more computer systems includinggeneral-purpose computer system 101 shown in FIG. 1. Computer system 101may include a general-purpose computer system that is programmable usinga high-level computer programming language. Computer system 101 also maybe implemented using specially programmed, special purpose hardware. Incomputer system 101, one or more processors 103 typically include acommercially available processor such as the well-known Pentium or Coreclass processors available from the Intel Corporation or the well-knownAthlon or Opteron class processors available from the AMD Corporation.Many other processors are available. Such a processor usually executesan operating system which may include, for example, the Windows-basedoperating systems (e.g., Windows NT, Windows 2000 (Windows ME), WindowsXP, Windows Vista operating systems) available from the MicrosoftCorporation, MAC OS System X operating system available from AppleComputer, one or more of the Linux-based operating system distributions(e.g., the Enterprise Linux operating system available from Red HatInc.), the Solaris operating system available from Sun Microsystems, orUNIX operating systems available from various sources. Many otheroperating systems may be used, and the instant invention is not limitedto any particular operating system.

The processor and operating system together may define a computerplatform for which application programs in high-level programminglanguages are written. It should be understood that the instantinvention is not limited to a particular computer system platform,processor, operating system, or network. Further, it should beappreciated that appropriate programming languages and appropriatecomputer systems other than those mentioned herein could also be used.

Various embodiments of the instant invention may be programmed using anobject-oriented programming language, such as SmallTalk, Java, C++, Ada,Python, or C# (C-Sharp), functional programming languages, scriptinglanguages such as JavaScript, and/or logical programming languages maybe used. Various aspects of instant invention may be implemented in anon-programmed environment, such as documents created in hypertextmarkup language (HTML), extensible markup language (XML) or other formatthat, when viewed in a window of a browser program, render aspects of agraphical user interface (GUI) or perform other functions. Variousaspects of instant invention may be implemented as programmed ornon-programmed elements, or any combination thereof. For example, someembodiments of the instant invention may be implemented using a set ofprogramming languages and techniques known as AJAX to provide a userwith a web-based editor interface.

Computer system 101 may also include one or more memory devices 105,such as a disk drive, memory, or other device for storing data,connected to the processor 103. Memory 105 is typically used for storingprograms and data during operation of the computer system 101.Components of computer system 101 may be coupled by an interconnectionmechanism such as network 107, which may include one or more busses(e.g., between components that are integrated within a same machine)and/or a network (e.g., between components that reside on separatediscrete machines). The interconnection mechanism enables communications(e.g., data, instructions) to be exchanged between system components ofcomputer system 101.

Computer system 101 may also include one or more input/output (I/O)devices 109, for example, a keyboard, mouse, trackball, microphone,touch screen, printing device, display screen 111, speaker, etc. Inaddition, computer system 101 may contain one or more interfaces (e.g.,network communication device 113) that connect computer system 101 to acommunication network 115 (in addition or as an alternative to thenetwork 107).

Computer system 101 may include one or more storage systems 117. Thestorage system 117 may include a computer readable and writeablenonvolatile recording medium in which signals are stored that define aprogram to be executed by the processor or information stored on or inthe medium to be processed by the program. The medium may, for example,be a disk or flash memory. Typically, in operation, the processor causesdata to be read from the nonvolatile recording medium into anothermemory that allows for faster access to the information by the processorthan does the non-volatile medium. This memory is typically a volatile,random access memory such as a dynamic random access memory (DRAM) orstatic memory (SRAM). The memory may be located in storage system 117,as shown, or in memory system 105. The processor 103 generallymanipulates the data within the integrated circuit memory 103, and thencopies the data to the medium associated with storage system 117 afterprocessing is completed. A variety of mechanisms are known for managingdata movement between the medium and integrated circuit memory elementand the instant invention is not limited thereto. The instant inventionis not limited to a particular memory system or storage system.

The computer system may include specially-programmed, special-purposehardware, for example, an application-specific integrated circuit(ASIC). Aspects of the instant invention may be implemented in software,hardware or firmware, or any combination thereof. Further, such methods,acts, systems, system elements and components thereof may be implementedas part of the computer system described above or as an independentcomponent.

Although computer system 101 is shown by way of example as one type ofcomputer system upon which various aspects of the instant invention maybe practiced, it should be appreciated that aspects of the instantinvention are not limited to being implemented on the computer system asshown in FIG. 1. Various aspects of the instant invention may bepracticed on one or more computers having different architectures orcomponents than that shown in FIG. 1.

Specifically, one or more portions of the computer system may bedistributed across one or more computer systems coupled to thecommunications network 115 such as computer systems 119A and 119B. Thesecomputer systems also may include general-purpose computer systems. Forexample, various aspects of the instant invention may be distributedamong one or more computer systems (e.g., servers) configured to providea service to one or more client computers, or to perform an overall taskor part of an overall task as part of a distributed system, as describedbelow. For example, various aspects of the instant invention may beperformed on a client-server or multi-tier system that includes programcomponents distributed among one or more server systems that performvarious functions according to various embodiments of the instantinvention, as described below. These components may include executable,intermediate and/or interpreted code which communicate over acommunication network (e.g., the Internet) using a communicationprotocol (e.g., transmission control protocol/Internet protocol(TCP/IP)). It should be appreciated that the instant invention is notlimited to any particular system or group of systems. Also, it should beappreciated that the instant invention is not limited to any particulardistributed architecture, network, or communication protocol.

Example Distributed System Architecture

FIG. 2 shows an architecture diagram of an example distributed system200 that may perform various aspects of some embodiments of the instantinvention.

For example, one or more computer systems may act as a user interfacesystem 201 that responds to requests from a user of the editor interface(e.g., a user of user computer 203). User interface system 201 maycommunicate with other computer systems (e.g., 205A-J, 207), to obtainand provide information that may be needed to respond to user requests,store information, track relevant data and events, and distribute emailmessages. Such computer systems may include, for example,general-purpose computer systems as discussed above with reference toFIG. 1.

It should be appreciated that FIG. 2 is used for example purposes only,and that other architectures may be used to facilitate one or moreaspects of the instant invention. For example, in some embodiments, eachidentified computer system of FIG. 2 may include a plurality of computersystems configured to perform the functions identified with the computersystems below. Additional and/or alternative functions or distributionsof functions may be performed by computer systems in other embodiments.

As shown in FIG. 2, distributed system 200 may be configured to performany functions, including but not limited to, storing, transmitting,editing, formatting, distributing, tracking, retrieving, and insertinginformation. The computer systems of system 200 may be coupled togetherby one or more communication networks 209, 211. Communication network209, in some implementations, may include the Internet. Communicationnetwork 211, in some implementations, may include a local area network(LAN). Firewall 213 may separate LAN 211 from the Internet 209 and allowonly desired communication to pass between LAN 211 and the Internet 209.

Each computer system of system 200 may be configured to perform aspecific function for system 200. For example, in one embodiment of theinstant invention, user interface system 201, as discussed above, may beconfigured to perform a plurality of functions related to providing aneditor interface to a user, such as receiving, transmitting, and/orprocessing hypertext transfer protocol (HTTP) messages, extensiblemarkup language hypertext transfer protocol (XMLHTTP) requests, and/orother electronic messages. To perform such functions, system 201 mayexecute one or more server processes (e.g., computer programs) thatreceive and respond to requests from one or more remote client systems(e.g., user computer 203). In one implementation, for example, userinterface system 201 may execute a WebSphere Application Sever 6.0process.

User interface system 201 may be configured to receive and transmitselectronic messages to and from user computer 203 through LAN 211,firewall 213 and the Internet 209. In some implementations, usercomputer 203 may be configured to execute a standard web browserprogram, such as Internet Explorer, that communicates with userinterface system 201. In some implementations, the web browser programmay be configured to execute one or more additional computer programs,such as a JavaScript program received from user interface system 201. Insome implementations, the web browser may be configured to display oneor more webpages based on AJAX. In some implementations, the web browsermay be configured to retrieve information for one or more webpages byusing an XMLHTTP request to a remote server (e.g., user interface system201) rather than reloading an entire webpage to provide a moreinteractive web-based experience to a user.

In some implementations, user interface system 201 may be configured toexecute one or more renderer processes (i.e., processes that outputrepresentations of email messages) that may be used, for example, togenerate a representation of an email message from a representation of adocument object model (DOM) (i.e., a collection of information such asobjects and classes that represent at least a portion of an emailmessage), as described in more detail below. In some implementations,user interface system 201 may also track customization of an emailmessage being edited by a user through an editor interface. For example,user interface server 201 may store an initial representation of anemail message when the editor interface is first provided to the user(e.g., by the user interface server 201). User interface server 201 maythen update the stored representation as the email message is customized(e.g., by recording updated representations of the email message sentduring server level processes, for example using HTTP messages).

In some implementations, user interface system 201 may be configured toexecute an email manager process. The email manager process may manageroperation of the renderers, tracking of DOM representations,communication of a database table, and any other desired emailmanagement functions.

According to one embodiment, computer system 205A may be configured toprovide spell checking for a user of user computer 203. For example,computer system 205A may execute a server process that checks thespelling of a received email message. If a user of computer 203 selectsto perform a spell check on an email message or part of an emailmessage, as described below, computer system 205A may perform the spellcheck on the email message or the part of the email message and providethe user with an indication of a result of the spell check.

According to one embodiment, image server 205B may be configured tomanage the storing and transmission of images. Images, for example, maybe image files incorporated into one or more email messages designed bya user of user computer 203. Images may be in any image format,including the well known Joint Photographic Experts Group (JPEG),windows bitmap (BMP), and graphics interchange format (GIF) formats. Insome implementations, image server 205B may also be configured toprovide images to recipients (e.g., a user of recipient computer 207) ofan email message designed by a user of user computer 203. In someimplementations, image server 205B may provide a copy of the images tomirror servers outside of LAN 211 to decrease communication throughfirewall 213 and within LAN 211 when users access those images (e.g.during editing, recipients of transmitted email messages).

According to one embodiment, database server 205C may be configured toprovide access to one or more databases. Database server 205C, forexample, may execute a well known database server process such as an SQLdatabase process (e.g., an SQL server available from the OracleCorporation, Red Shores, Calif.) configured to respond to SQL queries.Database server 205C may be configured to store and provide access toinformation related to a user of user computer 203, one or morerecipients of an email message, and/or information regarding one or morecustom email messages (e.g., a message customized through an editorinterface).

According to one embodiment, schedule server 205D may be configured toschedule transmission of completed email messages. For example, after auser of user computer 203 customizes an email message, the user mayidentify a plurality of recipients for the custom email message (e.g., auser of recipient computer 207). Schedule server 205D may schedule atransmission of a plurality of custom email messages to the plurality ofrecipients. Because a large number of email messages may be transmitted,schedule server 205D may perform load balancing operations (such asspreading the transmission over a period of times) so that thetransmission of email messages is distributed according to availableresources.

According to one embodiment, mail farm servers 205E may be configured totransmit custom email messages to a plurality of recipients. Mail farmservers 205E, for example, may retrieve an email message and a list ofrecipients from database server 205C according to an instruction fromschedule server 205D and transmit an email message to each recipientidentified by the list of recipients. Mail farm servers 205E may beconfigured to execute a well known Simple Mail Transmission Protocolprocess (SMTP) that performs mail transmission to remote computersystems. The email messages may be transmitted through firewall 213 andthe Internet 209 to a recipient using recipient computer 207.

According to one embodiment, email messages transmitted to a recipientmay be received by the recipient's internet service provider (ISP) mailserver 205F. In some implementations, ISP mail server 205F may store arepresentation of the email message until the recipient (e.g., using anemail client executed by recipient computer 207) retrieves the emailmessage. In some embodiments, ISP mail server 205F may perform spamfiltering and/or authentication of a transmitter of an email beforeallowing an email message to be transmitted to a recipient and mayreject some email messages that fail such filtering or authenticationprocesses.

According to one embodiment, bounce server 205G may respond to emailmessages that are rejected by ISP mail server 205F or otherwise are notproperly delivered to the recipient and are returned (i.e., “bounced”).For example, bounce server 205G may be configured to record informationregarding the rejection of the email message and to re-transmit therejected email message a predetermined number of times. In someimplementations, bounce server 205G, may include one or more serverssubstantially similar to mail farm servers 205E and/or may use mail farmservers 205E to perform some mailing functions.

According to one embodiment, domain name system (DNS) authenticationserver 205H may perform authentication for recipient ISP mail serversthat require a DNS authentication before allowing an email message to betransmitted to a recipient. For example, ISP mail server 205F maytransmit a request to authentic a domain name of the transmitter of theemail messages. In some implementations ISP mail server 205F may use thewell-known sender policy framework process to authenticate a sender byperforming a DNS query. DNS authentication server 205H may receive therequest and provide ISP mail server 205F with authentication, which mayinclude a list of authorized sender domains. In some implementations,DNS authentication server may include a well-known DNS server coupled toLAN 211 and/or the Internet 209.

Subscriber server 205I and tracking server 205J may provide servicesrelated to a recipient of an email message. For example, subscriberserver 205I may allow a recipient to subscribe and/or unsubscribe from arecipient list and may store such information in database sever 205C. Asanother example, click tracking server 205J may track and record whethera recipient opens an email message and/or selects any links within theemail message. These functions and servers are examples only. In variousembodiments, any desired set of services may be performed by any desiredset of recipient related servers.

Although separate computer processes and systems communicating with oneanother have been described, it should be understood that embodiments ofthe instant invention are not limited to any particular arrangements ofcomputer processes or systems. In some embodiments different processacts may be performed in addition and/or as an alternative to thedescribed acts. In some implementations, computer systems described asseparate may be a single computer system. In some implementations, acomputer system described as a single computer system may be multiplecomputer systems.

Example Process and Interfaces

FIG. 3 shows an example process 300 that begins at block 301 and thatmay be performed to create and distribute an email message according tosome embodiments of the instant invention. It should be understood thatprocess 300 is shown as an example only and that various embodiments ofthe instant invention may perform any set of acts in any desired orderto create and distribute email messages.

As indicated at block 303, process 300 may include receiving anindication of a selected template document. A template document mayinclude any data indicating an initial set of content and/or layout ofan email message. To facilitate selection of a template document by auser of an embodiment of the instant invention, a template selectioninterface may be provided to the user (e.g., by user interfaces system201). FIG. 4 shows an example template selection interface that may beused to select a template document from a plurality of templatedocuments.

In some embodiments, a template document may include information fromwhich an initial representation of an email message may be generated.Templates may be used by some implementations because they may ease theprocess of designing an email message. For example, templates may bedesigned by professional email designers to include elements, layoutsand formats that may be easily customized for particular needs.

In some implementations, the initial representation of the email messagemay include a plurality of content blocks positioned according to aninitial layout defined by the template document. In someimplementations, a template document may also include information thatmay be used to customize one or more controls of an editor interface.Such customization of controls may allow an email message based on atemplate document to be edited with a set of controls most optimized forthe base template document. In conventional email editing techniques,templates have been used (e.g., as a base for a document and/or wizard),however, templates have only been used with a standard set of controlsrater than to customize such controls.

In some embodiments, a template document may include an XML document.The XML document may define an email message that includes a pluralityof panels and blocks. In some implementations, the panel and blocksdefined in the XML document may be used to generate panel and blockobjects/wrappers in a JavaScript or other program. As described in moredetail below, a panel may identify a relative position within an emailmessage and any other desired characteristics associated with blockswithin that position. As described in more detail below, a block mayidentify content such as text and images as well as formatting of thecontent and any other desired characteristics of the content. In someimplementations, a panel of an email message may each include a number(e.g., 0 or more) blocks.

In some implementations, an initial representation of an email messagemay be generated based on a template document by generating the initialrepresentation having the content of a plurality of blocks defined inthe template document and the layout of a plurality of panels defined inthe template document. Accordingly, the template document may define aninitial layout and content of an email message by defining a pluralityof panels and blocks within those panels.

In some implementations, a template document (e.g., in the form of anXML document) may define a DOM. A DOM, for example, may represent awebpage viewable by a standard web browser, as is known in the art. Arepresentation of the DOM (e.g., the XML document itself, a treestructure defined by the XML document) may be use as input to a renderer(e.g., a renderer process executed by user interface system 201). Insome implementations, the representation of the DOM may include some orall of the basic information and options of an email message, asdescribed below with regard to process block 305. The renderer maygenerate an output HTML, text, or other formatted output based on theDOM and the configuration of the renderer. For example, in oneimplementation, a visual editor renderer may generate, at least in part,an HTML representation of an email message based, at least in part, onan input representation of a DOM.

In some implementations, renderer input may not be limited to a DOMbased on a template document. For example, the DOM input may include,for example, a DOM defined by a template document or a DOM defined by acustom email message, such as an email message that has previously beenpartially designed using an editor interface and saved by a user forfuture customization.

In some implementations, a visual editor renderer may accept an inputDOM that includes a plurality of panels and blocks. In this case, avisual editor renderer may add/or JavaScript and/or other programmingelements to add content and layout functionality to the DOM. A visualeditor renderer may then output at least a portion of a viewable webpagethat may be transmitted to a user. Operation of various examplerenderers is described in more detail below.

FIG. 4 shows an example template selection interface according to oneembodiment of the instant invention. As shown in FIG. 4, templatedocuments may be categorized into a broad set of categories listed in acategory list 401 and a subset of styles listed in a style list 403. Auser may select a template category from the category list 401 and astyle from the style list 403. In some implementations, a preview image405 of a selected template document may be displayed through theinterface to provide the user with an example of an email generatedusing the template document before the user selects a template document.When the user decides on a particular template, the user may select thenext control 407 or other control type to submit an indication of theselected template document.

In some embodiments of the instant invention, user interface system 201may receive an indication of the selected template document from theuser (e.g., from user computer 203) through a communication network suchas the Internet 209. In some implementations, the indication of theselected template document may include an electronic message, such as anHTTP message. In some implementations, the indication of the selectedtemplate document may include, for example, a template identificationnumber referencing a database table of template documents, a position incategory list 401 and style list 403 that may be used to identify theselected template document, and/or any other identifier that may be usedto identify a selected template document.

In some implementations, rather than a template document, a saved customemail message may be selected and treated substantially similar to atemplate document. In this case, a user may access previously editedemail messages through a saved email interface rather than a templateselection interface so that new messages may be generated based on thepreviously edited email message or the previously edited email messagemay be further customized.

As indicated at block 305, process 300 may include receiving anindication of basic information and options for an email message. Insome implementations, the basic information may include, for example, asubject of the email, a name of a sender of the email, an email addressof a sender of the email address, a reply email address, and/or otheremail header information. In some implementations one or more optionalelements, such as forwarding elements (e.g., a content element thatincludes a link to forward an email message to another email address),permission reminder elements (e.g., elements that remind a recipient whythey have received an email message and ask them to add a sender to anapproved sender list such as an email contact list), and subscriptionelements (e.g., elements that include a link to add and/or remove arecipient from a recipient list).

FIG. 5 shows an example interface that may be used by a user of anexample embodiment to submit such basic information and options. A user,for example, may enter information into information blocks 501. A usermay select one or more options using option selectors 503. When a useris satisfied with entered information and selected options, the user mayselect next control 505 to submit an indication of the basic informationand options to an embodiment of the instant invention (e.g., userinterface system 201).

In one example implementation, a system may receive the indication ofthe basic information and options from the user through a communicationnetwork such as the Internet 209. In some implementations, theindication of the basic information and options may be included withinone or more electronic messages, such as an HTTP message.

As indicated in block 307, process 300 may include presenting a userwith an editor interface. In some implementations, the editor interfacemay include an AJAX based webpage. However, it should be appreciatedthat other interface programming techniques may be used. The editorinterface may initially display an initial approximation of an emailmessage comprising a plurality of content blocks. In someimplementations, the initial approximation of the email message may begenerated based, at least in part, on a selected template document, asdescribed above. In some implementations, the initial approximation ofthe email message may also be based on entered basic information andoptions. In the case of an initial approximation being based off of atemplate document and/or other basic information and options, a user maybe presented with a base from which customizations may be made.

In some embodiments, the editor interface may accept customization tocontent and layout of the email message to generate a custom emailmessage. This may allow a user to flexibly generate a custom emailmessage. In some implementations, the editor interface may acceptcustomizations while displaying an approximation of an email message.This may allow a user to more readily appreciate the effect of acustomization. In some implementations, the editor interface maydisplay, to the user, a customized approximation of the email messagebased on the entered customizations as the user enters thecustomizations so that a user may see an approximation of a final outputemail in approximately real time. FIG. 6 shows an example of an editorinterface according to one embodiment of the instant invention.

In some embodiments, a visual editor may parse and replace elements ofan editor interface based on an interface being used to access thevisual editor by the user. For example, in some implementations a usermay access the visual editor using a web browser. Because certain webbrowsers render HTML differently and support different technologies, anHTML-based editor interface may appear differently in different webbrowsers. In some implementations, a web browsers' rich edit controlsare limited either in general functional or in browser specific ways; inthese cases HTML re-writing may be employed to enhance the functionalityof the Rich Edit Control or to more standardize the web browserbehavior.

FIG. 6 shows an example editor interface 600 displaying a portion of aninitial approximation of an email message (e.g., an email message beforeany customization) according to one embodiment of the instant invention.The email message may include a plurality of panel elements (e.g., 601,603, and 605). As discussed above with respect to the template document,a panel element may define a position within an email message. Forexample, header panel 601 defines an area at the top of the email thatspans the width of the email message, left column panel 603 defines anarea below the header panel on the left side of the email addressspanning about a third of the email, and top panel 605 defines an areabelow the header panel on the right side of the email and spanning aboutthe remaining two-thirds of the email message.

In one example implementation, the position of a panel may be defined bythe order in which the panels are defined in the selected templatedocument or later in a DOM associated with an email message. Forexample, a template document corresponding to the example template emailof FIG. 6 may include a table definition that defines a table elementhaving a width of 580 pixels (i.e., the width of the email message). Thetemplate document may next include a definition of header panel 601having a width of 580 pixels as well. The template document may nextinclude a definition of left column panel 603 having a width of 185pixels. The template document may next include a definition of top panel605 having a width of 380 pixels. In this example, a header panel 601may be placed at top of the template email message because the associatedefinition appears first in the template document. Next, left columnpanel 603 may be position top and left with a width that only spans partof the email message. And then top panel 605 may be positioned in theremaining space to the right of left column panel 603 because the widthof top panel 605 is less than the remaining width of the email message.It should be understood that the pixel values given above are describedas an example only.

In one example implementation, each panel may be defined by XML codethat corresponds to a portion of an AJAX based webpage. Left columnpanel 603 shown in the template email of FIG. 6 may be defined, forexample, in a selected template document as:

<tr>  <panel title=“Left Column”> <td valign=“top” width=“185”class=“QuicklinkBG”> </td> </panel> </tr>

In this example definition, left column panel 603 is empty (e.g.,contains no block elements), is defined to have a width of 185 pixels,is defined so that content within the panel is aligned to the top of thepanel, and is defined to use cascading style sheet class “QuicklinkBG”which may be defined elsewhere in the template document.

As shown in FIG. 6, a representation of an email message in editorinterface 600 may also include a plurality of content blocks 607, 609,611, 613, 615, and 617. Each block may include a type defined in thetemplate document selected by the user at block 303 of process 300. Forexample, block 607 includes a company logo block, block 609 includes atitle block, block 611 includes an introduction block, block 613includes an article block, block 615 includes a table of contents bock,and block 617 includes a signup box block. Contents and characteristicsof each block may also initially be defined by the template documentand/or the basic information and options received at block 305 ofprocess 300.

Similar to a panel as described above, each block may be defined by XMLcode that may correspond to a portion of an AJAX based webpage. Anexample definition of table of contents block 611 within left columnpanel is given by:

<tr>  <panel title=“Left Column”> <td valign=“top” width=“185”class=“QuicklinkBG”> <block title=“Table of Contents” type=“toc”> <tablecellpadding=“5” cellspacing=“0” border=“0” width=“100%”class=“BlockMargin”>  <tr> <td height=“20” class=“Title TitlePaddingTOCTitle”> <b><heading>In This Issue</heading></b></td> </tr> <toc> <tr><td width=“100%”><a class=“TOCLinks” href=“”>Article Headline</a></td></tr> </toc>  </table> </block> </td> </panel>

In this example, table of contents block 611 is defined to be withinleft column panel 603. Table of contents block 611 is defined to usecascading style sheet classes “BlockMargin,” “Title,” “TitlePadding,”“TOCTitle,” and “TOCLinks,” which may be defined elsewhere in theselected template document. Such cascading style sheet classes maydefine available and/or default font and\or background characteristics(e.g., color, style, etc.) for the block. Table of contents block 611 isdefined to include contents including a title with text of “In thisIssue,” and a table of contents element defined within the <toc> and</toc> tags which displays headlines of other blocks that are definedhaving a “toc” flag set to “true.” For example, an article block with a“toc” flag set to “true” may be defined, in part, as:

-   -   <block title=“Article Block” toc=“true”>.

In some implementations, an email message may be limited to a singletable of contents element and/or block. In some implementations, a tableof contents bar may include a refresh control that may be selected torefresh the table of contents list (e.g., determine if changes have beenmade to an <toc> tags and adjust a list accordingly).

In some implementations, additional special flags other than the “toc”flag may be included in some block definitions to identify specialfunctionality associated with a block. For example, in someimplementations, some blocks may incorporate partner incorporatedinformation. In some implementations, such blocks may include a specialpromotions flag to identify that the block information may reference anoutside source. In some implementations, such information may be used byone or more renderers in generating a representation of the emailmessage. For example, the renderers may search for such special flagsand perform a designated function in some modes. Particularly, withrespect to the promotions tag, a preview renderer when generating a liveversion of an email message may merge partner information into apromotions block.

In some implementations, multiple blocks may be positioned within asingle panel. For example, table of contents block 611 and signup boxblock 613 are positioned with left column panel 603 in the examplerepresentation of an email message in FIG. 6. Similar to the position ofpanels within an email message, as described above, the order of blockswithin a panel may be determined, in some implementations, by the orderthe blocks are defined within the panels (e.g., in a template documentor a DOM).

In addition to the initial approximation of the email message, editorinterface 600 includes a control panel 619. Control panel 619 mayinclude global and/or block specific functionality such as textformatting, content addition, block addition, anti-spam checking, undo,redo, spell checking, and/or preview operations. Control panel 619 mayinclude different control elements based on an edit operation/mode(e.g., by requesting an update to control panel 619 based on user inputby transmitting an XMLHTTP request to user interface system 201). Insome implementations, as is described in more detail below, controlelements included in control panel 619 may be based, at least in part,on the selected template document.

Through the editor interface 600 as shown in FIG. 6, a user maycustomize content and layout of a displayed email message. Variouscustomizations may be performed and/or stored at different processlevels within the computer systems associated with editor interface 600.These process levels may be arranged to provide a balance between speedof operations (e.g., spell check) and reliable persistence of data(e.g., storing content changes to a database).

For example, in one embodiment, customization may be divided into threeprocess levels: a client level, a sever level, and a database level. Theclient level may include a process performed on a user's computer system(e.g., through one or more programs, such as JavaScript programs,executed on user computer 203). The server level may includecommunication between the user computer 203 and user interface system201 so that user interface system 201 may track customization of theemail message (e.g., by storing information in local memory that isfaster than memory of a larger database server such as database server205C). The database level may include a persistent storage and/orretrieval of information to and/or from at least one database table(e.g., stored on database system 205C). Although an example of arrangingactions among these levels is described below, any desired arrangementamong these levels or arrangement of alternative or additional processlevels may be used with embodiments of the instant invention.

In some implementations, retrieval of a template document or otherwisesaved representations of an email message (e.g., from previously editedemail messages) to display a representation of a template email mayinclude a database level process. For example, in some implementations,the template document may be retrieved from a database server, byperforming a database query.

In some implementations, at least a portion of the functionality ofeditor interface 600 (e.g., customization of content, customization oflayout) may be enabled by a plurality of JavaScript programs hooked tospecific events (e.g., mouse clicks on controls such as add controls orcontrol panel 619 elements, mouse drags such as drags of a block orright clicking on an image, etc.). It should be understood that anyevents in addition to the customization events described below mayinclude hooked JavaScript events. It should also be understood that theinstant invention is not limited to a visual editor implemented usinghooked JavaScript events.

In some implementations of editor interface 600, a user may performlayout customization of an email massage, such as adding, deleting,and/or moving blocks among panels through editor interface 600. As theblocks are added, deleted and or moved, a displayed representation ofthe email may be updated to display a new approximation of the emailmessage.

FIG. 7 shows an example block adding interface 701 that may be used toadd one or more blocks through editor interface 600. An “Add Blocks”link of control panel 619 may be selected to access block addinginterface 701 through which a user may add a block at the end of apanel.

Controls available through block adding interface 701 may, in someimplementations, be defined, at least in part, by a selected templatedocument. For example, block adding interface 701 includes headerinterface 703, left column interface 705, top main interface 707,articles interface 709, and bottom main interface 711. In someimplementations, each of these interfaces may correspond to a paneldefined in a selected template document. For instance, header interface703 may correspond to header panel 601.

As is shown in FIG. 7, the types of blocks that may be added to eachpanel may be limited. In some implementations, blocks that may be addedto each panel may be defined, at least in part, by a selected templatedocument. In some implementations, a panel interface (e.g., 703, 705,707, 709, and 711) may include block add controls for each blockoriginally positioned within an associated panel in a selected templatedocument. For example, header interface 703 includes a company logoblock add control 713 and a title block add control 715. A selectedtemplate document corresponding to the email message may include aheader panel 601 having a company logo block 607 and a title block 609corresponding to add controls 713 and 715.

In some implementations, a panel interface (e.g., 703, 705, 707, 709,and 711) may only include add controls for “cloneable” blocks positionedwithin an associated panel in a selected template document. A cloneableblock may include a block having a <clone> tag set to true (or not setto “false”). For example, with respect to the example article interface709, an article block within an article panel may be defined in part as:<block title=“Article Block” clone=“true”>, and with respect to top maininterface 707, article block 613 within top main panel 605 may bedefined as <block title=“Article Block” clone=“false”>. In someimplementations, a default value of the <clone> tag may be true, so thata block is cloneable unless the attribute is set to “false.” In someimplementations, the number of cloned copies of a block that may beadded to an email message may be limited to a maximum number (e.g., 30).

In some implementations in which a template document includes multipleblocks of a single type in a panel, only one of the multiple blocks mayhave a <clone> tag set to true. Whenever a new block of that type isadded to the panel, the block with the clone attribute set to true maybe copied and added at the end of the desired panel.

In some implementations, an intermediate representation of a blockand/or panel may be displayed to identify an approximate position wherea block may be added. A panel may be identified to the user to aid indetermining which block to add to which panel. For example, if a userpositions a cursor within header interface 703, outline 717 may appeararound header panel 601. In some implementations, outlining the panelmay include a client level process.

A user may add a block into a panel by clinking the add control next tothe block's name in block interface 701. The selected block may be addedto the selected panel after the user selects the respective add control.The block added may be a copy of a cloneable block's defined by aselected template document (e.g., the block's contents may be the sameas a block default content defined in the selected template document).In some implementations, the copied block may include a cloneable blockof the desired type, as described above.

Adding a block, in some implementations may include a server levelprocess. For example, adding a block may cause an entry to be added to aDOM stored by a web browser executing on the user's computer (e.g.,adding a block node to a panel node of a DOM) and may cause atransmission to be made to user interface system 201. The transmissionmay include a representation of the updated DOM. In someimplementations, the remote server may be configured to track theaddition of a new block by storing the representation of the updated DOMin local memory (e.g., random access memory (RAM), hard disks, etc).

Some embodiments of a visual editor may allow a user to delete blocks.For example, in editor interface 600, company logo block 607 may bedeleted by selecting delete control 719. In some implementations, adelete control may include a familiar “X” close control used to closemany traditional computer applications. In some implementations, a usermay be warned and/or asked to confirm before a block is deleted.

Deleting a block, in some implementations may include a server levelprocess. For example, deleting a block may cause an entry to be deletedfrom a DOM stored by a web browser executing on the user's computer(e.g., deleting a block node of a panel node of a DOM) and may cause atransmission to be made to user interface system 201. The transmissionmay include a representation of the updated DOM. In someimplementations, the remote server may be configured to track theaddition of a new block by storing the representation of the updated DOMin a local memory.

In some implementations, a visual editor may allow a user to move ablock from an initial position to a desired position (e.g., from onepanel to another panel, from an initial position in a panel to desiredposition in the same panel). FIG. 8 shows editor interface 600 in whichan article block 801 is being moved into header panel 601.

In some implementations, a block may be moved, for example by selectingand dragging a movement bar of the block. For example, FIG. 8 shows acompany logo block movement bar 803. In some implementations, as shownin FIG. 8, a block is being dragged, the block is displayed in apartially transparent manner (e.g., article block 801). A position ofarticle block 801 may correspond to a location of a cursor within editorinterface 600.

In some implementations, a JavaScript program may monitor select anddrag events and enable at least a portion of the movement functionalityof editor interface 600. For example, in one implementation, each blockin a representation of an email message displayed through editorinterface 600 may include an HTML table wrapped by a JavaScript objectenabling the movement functionality. In some implementations, forexample, a JavaScript object may await a mouse down event at aparticular location (e.g., on a movement bar of a block). When the mousedown event occurs, contents of a respective block may be copied to adrag item JavaScript object, which may include an HTML span elementwrapped by JavaScript. The drag object may be sized to match theoriginal block's size, a fade effect may be applied so that the dragobject appears transparent, and the drag object may be moved along witha cursor movement. Furthermore, when the mouse down event occurs, theoriginal block may be hidden so that it appears to be dragged from itsoriginal location along with a cursor.

In some implementations, an intermediate representation of a block movemay be indicated to illustrate where a block may be positioned. Forexample, as shown in FIG. 8, as a block is being dragged, a location inwhich the block may be placed if the block is dropped at a currentcursor position is indicated. Particularly, outline 805 indicates thatarticle block 801 may be placed in the position of outline 805 ifarticle block 801 is dropped in its current position. The outlinedcursor position may, in some implementations, correspond to a positionwithin a nearest panel to the cursor position (e.g., header panel 601).

In some implementations, a size of the indication (e.g., outline 805) ofthe new position may correspond to a size that the block being movedwould be if dropped into the new position. For example, article block801 may be approximately the size outline 805 the block is moved intothe location indicated by outline 805. The size of the block in the newposition may be different then in the block in the old position becausethe old position may include a panel of different proportions (e.g., toppanel 605) that the new position (e.g., header panel 601). In someimplementations, other blocks may be repositioned to approximate a newlayout as the block is being moved.

In some implementations the indication functionality described above maybe enabled using a normally hidden preview HTML table with dashed lineborder may be used to provide such position preview functionality. Forexample, after a mouse down event tracked by a drag item object, mousemovement may be monitored until a mouse up event. The normally hiddenpreview HTML table may continue to be repositioned along with mouse moveevents before such a mouse up event. On a mouse over event of anotherblock within the email message, in some implementations, the normallyhidden preview HTML table may be resized to match a block being moved,inserted and unhidden before or after the moused over block. Whethernormally hidden preview HTML table is positioned before or after themoused over block may depend, for example, on a cursor position. Forexample, in some implementations, if the mouse over event occurs in atop half of a block, the normally hidden preview HTML table may beinserted before the moused over block, but if the mouse over eventoccurs in the bottom half of the block, the normally hidden preview HTMLtable may be inserted after the moused over block. Such functionalitymay provide the user with a movement experience that may be expected ontraditional desktop applications rather than web-based applications.

In some implementations, when a user releases a mouse control afterdragging a block to a desired position (e.g., drops the block in thedesired position), the block may be placed in the desired panel in anorder corresponding to the desired location. For example, on a mouse upevent, a block being hidden, as discussed above (e.g., the originalblock that was the target of a mouse down event), may be deleted from anold position and inserted before a normally hidden preview HTML tableblock and then the normally hidden preview HTML table block may behidden again.

In some implementations, movement of a block may correspond to a blocknode being removed from an old panel node of a DOM and added to the newpanel node of the DOM or an order of block nodes of a single panel nodebeing changed.

In some implementations, a panel may be configured to provide a wrappingfunctionality for blocks within the panel as blocks are added, deleted,and/or moved. For example, a promotions panel 901 shown in FIG. 9contains three blocks horizontally across the panel in a firsthorizontal row 903 and two blocks across the panel in a secondhorizontal row 905. The blocks in this panel may be configured to wrapfrom first row 903 to second row 905 so that panel locations towards atop left location are filled first. Specifically, if a top right blockis moved to a bottom middle location, the bottom left block may be movedto the top right location, and the bottom middle block may be moved tothe bottle left location.

In some implementations, functionality associate with a block beingmoved (e.g., insertion of temporary blocks, display of partlytransparent block) may include a client level process. The process maybe performed, for example, by a JavaScript program executed by theuser's computer.

In some implementations, placement of a block in a desired location mayinclude a server level process. When the user places the block in thedesired location, a document object model maintained by the client's webbrowser may be updated to reflect a new order and location of blockswithin panels. The web browser may also transmit an indication of theupdated layout to user interface system 201. User interface system 201may store the information (e.g., a representation of an updated DOM) ina local memory.

In some embodiments, in addition to layout changes, a user may makeglobal formatting changes through control panel 619. In someimplementations, the global formatting changes may include textualformat changes and/or graphical format changes. For example, a user mayselect on a “Global Colors & Fonts” link of control panel 619 to accessa global formatting element 1001 as shown in FIG. 10. Similar to addblock interface 701, in some implementations, access to globalformatting interface 1001 may include a client level process that doesnot communicate to a remote server to display global formatting element1001. By providing access to global formatting element 1001 as a clientlevel process, such access may be provided quickly and seamlessly.

In some implementations, option available through global formattingelement 1001 may be based, at least in part, on a selected templatedocument. For example, in some implementations, the options availablethough global formatting element 1001 may correspond to cascading stylesheet classes defined within the selected template document.

For example, global formatting element 1001 includes a quick linksformatting interface 1003, a table of contents title formattinginterface 1005, a table of contents links formatting interface 1007, amain text formatting interface 1009, a body background formattinginterface 1011, a left column background formatting interface 1013, aheader background formatting interface 1015, and a footer imageformatting interface 1017. Each of these interfaces may correspond to acascading style sheet class defined in the selected template document.Specifically, quick links formatting interface 1003 may correspond to aquick links class defined as:

.QuickLinks{ title: Quick Links; font-family:Arial,Helvetica,sans-serif; font-size: xx-small; color: #333333;text-decoration: none; }.

In some implementations, each cascading style sheet class included in aselected template document may have a corresponding formatting interfacein global formatting element 1001. In some implementations, a classelement, such as the title element included in the quick links classdefined above, may act as a toggle for inclusion in global formattingelement 1001. For example, any class having a title element may alsohave a corresponding interface in global formatting element 1001 and anyclass not having a title element may not have a corresponding interfacein global formatting element 1001. Other elements may act as toggles inother implements so that desired controls may be included and un-desiredcontrols may be excluded.

In some implementations, all elements of a defined class may beformattable through global formatting element 1001. In someimplementations, only a subset of available elements may be formattable.For example, quick links formatting element 1003 only allows formattingof a font, a font size and a font color of the quick links class. Quicklinks formatting element 1003 does not allow formatting of atext-decoration element despite that element being present in the quicklinks class definition. In some implementations, a visual editorrenderer may determine which elements are formattable and which are notformattable before providing editor interface 600 to the user and maygenerate an appropriate portion of webpage including editor interface600.

In some implementations, individual class interfaces may allow differentelement editing based on the elements defined for a class. For example,the quick links class defines font style, font size, and font color, sothose elements may be formattable. The body background class may definea color, so body background interface 1011 may include a color selector1019 that may allow a user to select a new color for the body backgroundclass. Similarly, header background class may include an image, soheader background interface 1015 may include an image selector 1021 thatmay allow a user to select a new image. In some implementations, animage selector 1021 may include a separate user interface (e.g., aseparate webpage) through which a user may select a generic image orupload a custom image).

In some implementations, a global change made through global formattingelement 1001 may affect any element of the email that is defined by arespective cascading style sheet class. For example, a change to thequick links class through quick links interface 1003 may affect all textassociated with the quick links class.

In some implementations, making a global change through globalformatting element 1001 may include a server level process. For example,a DOM node corresponding to a changed cascading style sheet class to bechanged in a DOM stored by a web browser executing on the user'scomputer and may cause a transmission to be made to a remote server(e.g., user interface system 201). The transmission may include arepresentation of the updated DOM. In some implementations, the remoteserver may be configured to track the change to the cascading stylesheet class by storing the representation of the updated DOM in a localmemory.

In some implementations, global formatting element 1001 and/or controlpanel 619 may provide a user with one or more theme options (not shown).Such theme options may include, for example, changes to color schemesand/or style sheet classes of a particular email message being editedthrough editor interface 600. A user, for example, may select a themeelement (not shown), such as a drop down box, to select a theme. Thetheme, for example, may include a set of colors (e.g., font colors,background colors, border colors, etc.) and/or a set of style sheetclass definitions (e.g., new definitions for the already existingclasses in a selected template document). A representation of the emailmessage with the new colors and/or style sheet class may then bedisplayed to the user through editor interface 600. Theme functionalitymay include a server level process allowing tracking by user interfacesystem 201.

In some implementations, control panel 619 may provide a user with undofunctionality for layout and global formatting changes. For example,because a user may make mistakes, control panel 619 may include an“undo” control that may be selected to undo a previous block add, blockdelete, block move, and/or global formatting change. In someimplementations, to provide such undo functionality, indications ofoperations (e.g., block moves) may be stored in a stack as theoperations are performed. The stack may be stored by a program executedby a user computer (e.g., a JavaScript program, a web browser). Thestack may be “popped” to determine an immediately previous operationwhen the user selects the “undo” control. Once the previous operation isdetermined, a reversal of the operation may be performed (e.g.,returning a block to a previous position). In some implementations, alimited number of operations may be stored in a stack allowing only alimited number of operations to be undone. In some implementations, anundo function may include a process level similar to the undoneoperation.

In some embodiments, in addition to customization of layout and globalformatting, as described above, a visual editor may allow a user to editcontent of one or more blocks. FIG. 11 shows an example of content ofarticle block 801 being edited through editor interface 600. A user, insome implementations may edit an individual block by selecting an editcontrol such as edit control 1023 shown in FIG. 10.

As shown in FIG. 11, in some embodiments, a user may customize contentof a block. For example, a user may edit textual information, graphicalinformation (e.g., images, backgrounds, colors), data-driveninformation, partner information, and/or link information.

In some implementations, to provide content editing functionality, acontent editing interface may be provided to the user through editorinterface 600. In some implementations, the content editing interfacemay include an HTML Iframe hidden from view of a user before the userselects an edit control of a block. When the user selects an editcontrol of a block, the Iframe may be resized and repositioned over theblock and the contents of the block may be copied to the Iframe. Theuser may then perform edit content of the Iframe. When the user isfinished editing the content of the Iframe, the content may be copiedback to the block and the Iframe may be hidden once again.

In some implementations using cascading style sheet classes, copying thecontents of a block may include converting cascading style sheet tags toinline style tags. Conversely, copying the contents of the Iframe to theblock may include converting the inline style tags to cascading stylesheet class tags. The cascading style sheet class tags may be convertedto inline style tags to allow a user to alter individual attributes of ablock because cascading style sheet tags take precedence over inlinestyle tags in some web browsers. For example, if a block of text isattributed a class tag that defines a cascading style sheet class with abold style and a sixteen point font and the same block of text isdefined with an inline tag that identifies a twelve point font style,the sixteen point bold class tag may take precedence over the twelvepoint inline style tag even if the attribute tag is entered at a latertime.

To overcome this potential conflict, some implementations may convertall cascading style sheet class tags to inline style tags. When a styleis altered, the inline style tags may be changed to reflect the change.In some implementations, when the editing is complete and the userselects a save control, any changed inline tags may remain as inlinetags since they may no longer correspond to a defined style class andany unchanged inline tag may be converted back to cascading style sheetclass tags.

In some implementations, the conversion from class tags to inline tagsand the display of the Iframe may include a client level process. Thesefunctions may be performed, for example, by a JavaScript programexecuted by the user's computer.

As shown in FIG. 11, when the Iframe is displayed, a user may type intothe Iframe (e.g., article block 801) to edit text content. As a usertypes, changes to the text may appear in the edited block. In someimplementations, a block may be limited to a maximum number ofcharacters. For example, in one implementation, a block may be limitedto a maximum of 15,000 characters.

In some implementations, when a user selects an edit control (e.g.,1023) control panel 619 may change to include a block interface 1101.Block interface 1101 may include options for changing a font style, sizeand color as well as formatting of a paragraph, editing a backgroundcolor, and/or any other desired editing functions.

In some implementations, a user may also make formatting changes throughthe controls of block interface 1101. A user, for example, may highlighta target text and then select make a desired formatting change throughblock interface 1101. The target text may be changed to incorporate thedesired formatting change.

In some implementations, a user may also insert one or more specialcontent elements within a block using block interface 1101. For example,a user may insert an image, a hypertext link, and/or a data drivenelement through block interface 1101. In some implementations, a usermay also insert a partner element.

In one implementation, selecting a link element 1103 may display a linkinterface (e.g., through a separate webpage). An example link interfaceis shown in FIG. 12. As shown, the link interface of FIG. 12 may allow auser to enter information regarding a link to be inserted. Theinformation may include, for example, a link destination (e.g., a URL)and a link name (e.g., an identifier that may be displayed in thecontent of the block in place of the link).

In some implementations, when the user selects an “insert” control of alink interface such as the one in FIG. 12, the link may be inserted intothe block (e.g., 801) being edited through editor interface 600. In someimplementations, if the user entered the link interface by selectinglink element 1103 with text highlighted, the highlighted text may becomethe name of the link. For example, the word “appealing” in block 801 ofFIG. 11 comprises such a name of a link. In some implementations, a linkuniversal resource locator (URL) and/or a link name may be limited to amaximum length. For example, in one implementation, a link name may belimited to 15,000 characters and a link URL may be limited to 510characters. In some implementations, a link URL may be validated tofollow a valid URL format before a link may be inserted into an emailmessage.

In one implementation, selecting image element 1105 may bring up animage interface (e.g., in a new webpage) through which a user may uploadan image to image server 205B and/or insert an image into the blockbeing edited (e.g., block 801). FIG. 13 shows an example imageinterface. As shown, the image interface allows a user to enter alocation and description of an image file through upload interface 1301and to upload the image by selecting upload control 1303. An imageinterface may also allow a user to select from previously uploadedimages through selection interface 1305, and enter formattinginformation, such as making the image link and entering image alignmentdetails through image formatting interface 1307. A user may then insertan image at a cursor location within a block being edited (e.g., block801) by selecting an insert control 1309. In some implementations, asimilar image interface to the one shown in FIG. 13 may allow a user toenter a URL for an image rather than or in addition to a local imagelocation as in the upload interface of FIG. 13.

In some implementations, a user may manipulate a previously insertedimage of a block being edited (e.g., block 801). For example, in someimplementations, a user may select and drag and image from one locationwithin the lock to another location to move the image within the block.In some implementations, a user may right click and/or double click animage to access an image menu 1107 associated with the image.

In some implementations, image menu 1107 may include a set of imagemanipulation options. For example, as shown in FIG. 11, image menu 1107may include a change option, a resize option, and a delete option. Insome implementations, a user may select a change option to access animage interface substantially similar to the one shown in FIG. 13. Insome implementations, a user may select a delete option to remove animage from the block. In some implementations, even though an image maybe removed from a block, the image may remain in an image libraryassociated with the user and/or the email message and may be accessed(e.g., added) to another block (e.g., through the image interface shownin FIG. 13) at a later time without re-uploading the image. Selectingthe resize option may display a resize interface (e.g., in anotherwebpage) through which a user may adjust a size of the image. FIG. 14shows an example resize interface through which a user may scale animage and adjust height and width dimensions directly as well as previewa resized image before finishing a resizing.

In some implementations, subscriber element 1109 may allow a user toinsert data driven elements into a block being edited (e.g., block 801).For example, subscriber element 1109 may include a drop down list ofstored subscriber information, such as first name, last name, emailaddress, title, etc. Such data driven elements may be inserted into theblock at a location of a cursor and may appear as a generic elementduring editing. For example, FIG. 11 shows a data driven element 1111that references a recipient's first name. Before transmission of theemail, each recipient's first name may be inserted into the data drivenelement 1111, for example by accessing a database that stores eachrecipients' first name and inserting the name in the place of datadriven element 1111 in a respective copy of the email.

In some implementations, a greeting element 1113 may allow a user toinsert a custom greeting. For example, selecting greeting element 1113may display a greeting interface. FIG. 15 shows an example greetinginterface. As shown in FIG. 15, a greeting interface may allow a user toenter initial greeting text (e.g., though text box 1501), a data drivenelement (e.g., through data driven selector 1503) and an ending text(e.g., through text box 1505) for a primary greeting. A user may alsoenter a secondary greeting through secondary greeting element 1507. Insome implementations, a secondary greeting may be used in place of agreeting if a data driven element selected through data driven selector1503 is not available for a particular recipient. A user may insert agreeting object into a block by selecting a save control 1509.

In some implementations, a greeting object included in an email messagemay be partially read only. For example, a greeting object may beuneditable by selecting the greeting and typing into the greetingobject. Rather, the greeting may only be editable through the greetinginterface. This special treatment of greeting links may be useful toremind users that all data driven elements like those that typicallyappear in greetings (e.g., names) may not be available for allrecipients of an email and that a secondary greeting may be useful. Insome implementations, primary and secondary greetings may be merged withdata driven elements/selected by a preview renderer generating liveversions of a message to transmit to recipients at a later time.

In some implementations, a greeting interface may be accessed through agreeting menu by right clicking or double clicking a greeting object,similar to an image menu described above. In some implementations, agreeting menu may provide a user a set of options to manipulate agreeting. For example, in one implementation, a greeting menu may allowa user to delete greeting and to access a greeting interface such as theone shown in FIG. 15.

In some implementations, block interface 1101 may include a partnerintegration element (not shown). In some implementations, a user mayaccess a partner integration element (e.g., a drop down menu, one ormore buttons) to enable, disable, and/or edit partner integration withina particular block. In some implementations, partner integration mayallow a user to include access to and/or information from a partner. Apartner, in some implementations, may include a remote website thatprovides access to an API through which information and/or access to thewebsite may be integrated into an email message. In someimplementations, partners may include Amazon.com, PayPal.com, FTD.com,and/or any other desired website.

In some implementations, when a user selects a partner integrationelement, a partner integration interface may be displayed. In someimplementations, a partner integration interface may be uniform for allpartners. In some implementations, a partner integration interface maybe different for different partners. FIGS. 16 and 17 show two examplepartner integration interfaces through which a user may enter/editpartner integration information to generate/edit a partner integrationportion.

FIG. 16, for example shows a PayPal.com partner integration interfacethrough which a user may enter information such as product name, productimage URL, product description, product URL, product SKU, price, a buynow control URL, a buy now link text, and a learn more link text. Insome implementations, a user may insert a partner integration portionintegrating the entered information into a block being edited bycompleting the information and selecting an add control (not shown). Insome implementations, through such an interface, a recipient of an emailmessage may purchase an identified product by sending a PayPal.compayment to the user.

FIG. 17, for example shows an Amazon.com partner integration interfacethrough which a user may enter a product Amazon standard identificationnumber (ASIN)/international standard book number (ISBN). In someimplementations, such a number identifies a product to Amazon.com andinformation such as product description, product images, buy nowcontrols, product price, etc. may be integrated into a block beingedited from Amazon.com.

In some implementations, before a user may include a partner integrationportion into an email message (e.g., into a block), a user may be askedor required to enter information regarding membership with one or morepartners. For example, before a user integrates a PayPal.com portion,the user may be asked to provide a PayPal.com identification (ID) emailaddress and/or a completed payment URL identifying a PayPal.com accountto which payments may be sent. Before integrating an Amazon.com portion,a user may be asked to provide an Amazon.com associate ID identifyingthat may be used to identify the user to Amazon.com. In someimplementations, such membership information may be used for eachpartner integration portion for a respective partner in a particularemail message. In other implementations, different membershipinformation may be used for each partner integration portion even forthe same partner within the same email message.

In some embodiments, because users may misspell words, block interface1101 may provide a user with a spell check option. For example, a usermay access a spell check interface though block interface 1101 byselecting spell check control 1113. FIG. 18 shows an example spell checkinterface. As shown, in some implementations, a spell check interfacemay identify words that are not part of a library of known words (e.g.,words 1801 and 1803) with an indication, such as an underline orhighlight. In some implementations, a spell check interface may suggestwords from a library of known words that are similar to the identifiedwords through a suggestion interface 1805. In some implementations, auser may change an identified word to a suggested word, ignore anidentified word, add an identified word to a library of known words,change an identified word to a non-suggested word, or cancel a spellcheck through a change interface 1807. In some implementations, changeinterface 1807 may cycle through identified words (i.e., unknown words)from a first to a last word suggesting alternative words.

In some implementations, spell check functionality may be provided by aspell check server 205A. In some implementations, for example, when auser selects a spell check control, a representation of textual contentof a block being edited (e.g., block 801) may be transmitted to spellcheck server 205A. Spell check server 205A may perform a spell checkprocess to identify unknown words and provide a user with a spell checkinterface such as the interface of FIG. 18 in a new webpage.

In some implementations, a user may apply changes made through the spellcheck interface by selecting apply control 1809. In someimplementations, the changed textual contents of the spell checkinterface may be copied back to the block being edited (e.g., block 801)in editor interface 600 after the user selects apply control 1809.

In some implementations, a spell check may be performed using a trackedrepresentation of an email message in memory of user interface server201. By using such information to perform a spell check, the spell checkmay be performed more quickly than if a database query were performed toretrieve a stored representation of an email message from a databaseserver (e.g., 205C).

In some embodiments, to provide further customization options toadvanced users, block interface 101 may provide a user with a code viewoption. For example, a user may access a code view interface throughblock interface 1101 by selecting code view control 1115. FIG. 19 showsan example code view interface 1901. As is shown, in someimplementations, a code view interface 1901 may display HTML codecorresponding to the contents of a block being edited (e.g., block 801).A user having HTML coding skills may enter HTML code into code viewinterface 1901. Such an interface may allow a user more flexibility thanthe formatting and content editing otherwise available for a content ofa block by allowing the user to enter any HTML tags desired for aparticular block. In some implementations, when a user is finished witha code view interface 1901, the user may select an update control 1903to incorporate the changes into a block being edited (e.g., 801).

In some implementations, a code view option may allow a user to accessemail design options that may otherwise be inaccessible. For example, inone implementation, opentracking of an email message (e.g., trackingwhich recipients open an email message) may be enabled for all emailmessages by default. In some implementations, a user, however, mayaccess a code view option and include an <OpenTracking track=“false”>tag to disable opentracking for a particular email message.

In some implementations, because users may make mistakes when editingcontent of a block, block interface 1101 may provide a user with undoand redo functionality. For example, block interface 1101 may include anundo control 1117 and a redo control 1119. In some implementations, undocontrol 1117 may be selected to indicate an undo request for a previousediting or formatting of content of a block being edited (e.g., block801). In some implementations to provide such undo functionality,indications of editing operations (e.g., adding an image, formattingtext, etc.) may be stored in a stack as they as they are performed to ablock. The stack may be stored by a program executed by a user computer(e.g., a JavaScript program, a web browser). The stack may be “popped”to determine a previous editing operation when the user selects undocontrol 1117. Once the previous editing operation is determined, areversal of the editing operation may be performed to return contents ofthe block being edited (e.g., 801) to a state before the determinedediting operation was performed. In some implementations, a limitednumber of operations may be stored in a stack allowing only a limitednumber of operations to be undone.

In some implementations, a user may indicate a redo request for anundone operation by selecting redo control 1119. To provide redofunctionality, some implementations may include a redo stack that storesundone operations. For example, when an undo stack is “popped” toretrieve an indication of a previously performed editing operation, theindication may be “pushed” onto the redo stack. When redo control 1119is pushed, the redo stack may be “popped” to determine a previouslyundone operation that may then be reapplied to the block being edited(e.g., block 801). A redo stack may be cleared, for example, after eachcustomization performed by a user other than an undo, so that the redostack is only populated after an undo operation.

In some implementation, editing and formatting of content of a block(e.g., block 801) may include a client level process. A current state ofthe block may be stored, for example, by a program on a user computer(e.g., a web browser and/or JavaScript program). In someimplementations, spell checking and image uploading may be consideredclient level processes despite contact with a remote server because insuch implementations, spell checking and image uploading may not includetracking a state of an email message by user interface system 201.

In one embodiment, a user may select a cancel control 1121 or a savecontrol 1123 to complete an editing operation of a content block.

In some implementations, the user may select cancel control 1121 toreturn the content of a block being edited (e.g., block 801) to itsprevious state (e.g., before editing began.) To implement suchfunctionality, the web browser delete the content of the visible Iframeused to edit the block and hide the Iframe again, thereby displaying theunderlying original block. In some implementations, after the userselects cancel control 1121, editor interface 600 may return to a statesimilar to the one shown in FIG. 6 in which blocks may be moved, added,deleted, or selected for editing. In some implementations, canceling anedit may also clear an undo and redo stack. In some implementations,canceling an edit may not, however, remove uploaded pictures from animage server (e.g., 205B) even though an image may removed from theblock being edited if the image was inserted during a canceled editsession.

In some implementations, a user may select save control 1123 to save theedits made to a block being edited (e.g., block 801). In someimplementations, if save control 1123 is pressed, the contents of anIframe in which edits are being made may be copied to the original blockreplacing the original content of that block and the Iframe may behidden again. In some implementations, after the user selects savecontrol 1123, editor interface 600 may return to a state similar to theone shown in FIG. 6 in which blocks may be moved, added, deleted, orselected for editing. In some implementations, saving edits may alsoclear an undo and redo stack.

In some implementations, a save function may include a database levelprocess. A save function may include a database level function becausesaving to a database stores content changes to a persistent memory thatmay be maintained even if a user unexpectedly ends an editing sessionwithout otherwise saving changes. For example, a representation ofcurrent content of the edited block may be transmitted to a userinterface system 201 and used to update a representation of the currentemail message stored in a local memory on user interface system 201.User interface system 201 may then transmit determine if a priorrepresentation of the email message has been stored to in a databasetable (e.g., on database server 205C). If a prior version has beensaved, user interface system 201 may transmit a representation of theedited block to replace a previous representation of the block in thedatabase table. If no prior version has been saved, user interfacesystem 201 may transmit a complete representation of a current state ofthe email message to the database server (e.g., 205C) to be stored inthe database table.

The above described content and layout editing functionality may applyto a plurality of standard blocks in an email message. In someimplementations, one or more special blocks may also be included thatmay be subject to limited and/or special editing treatment. FIG. 20, forexample shows an example special block, physical address block 2001.Such special blocks, may, for example be used to include content thatmay be required by law or desired by a provider of the visual editor(e.g., advertisements). For example, some jurisdictions' anti-spam lawsmay require certain email messages to include an address of a sender asis included in physical address block 2001.

In the example implementation of physical address block 2001, delete,movement and adding functionality has been disabled. Initial content ofphysical address block 2001 may be supplied from a profile of a user ofthe visual editor or basic information such as that entered at block 305of process 300. In some implementations, physical address block 2001 anedit control selected to edit physical address block 2001 through aspecial block editing interface, an example of which is shown in FIG.21. A user, for example may enter new physical address information andmay save the new information by selecting the save control 2101. Savingcontent of a physical address content element may be a database levelprocess similar to saving edited content of other content blocks.

FIG. 20 shows a footer element 2003 that is another example of a specialblock. In some implementations, footer element 2003 may not bedeleteable, moveable cloneable, or editable through editor interface600. In some implementations, footer element 2003 may include requiredinformation and/or advertising information for a provider of editorinterface 600 (e.g., Constant Contact). In some implementations, a usermay select option regarding footer element 2003 through an interfacesimilar to the physical address interface or the basic information andoptions interfaces, both described above. For example, in someimplementations, a user may select a language for footer element 2003,select a design from among a plurality of footer designs, and/or choosea custom footer at process step 305, described above.

Through editor interface 600, a user may perform any number of contentand layout customizations to any number of blocks. When the user isfinished, or believes he or she is finished, or wants to preview theprogress of the design in a manner better resembling a final output, theuser may select on preview control 621, shown in FIG. 6.

When the user selects preview control 621, a request may be made to aserver (e.g., user interface system 201) to provide a preview of acustom email message. In some implementations, the server may respond bygenerating the preview (e.g., using a renderer as described below) andby transmitting a representation of a preview of the custom emailmessage to the user.

FIG. 22 shows an example implementation of a preview interfacedisplaying a preview representation. In some implementations, as shownin FIG. 22, a preview interface may include a preview pane in which apreview representation of the custom email message is displayed. Thepreview pane may display a current state of an email message that hasbeen edited by the user through editor interface 600, including a headerelement but excluding editing elements such as borders, title bars andcontrol buttons that may be displayed in editor interface 600 to enableediting functionality. In some implementations, the previewrepresentation may include an approximation of the custom email messageas the custom email message may appear to a recipient of the customemail message (e.g., through an email reading client).

In some implementations, preview generation may include a server levelprocess. In some implementations, the representation of the preview ofthe custom email message may be generated by a preview renderer. In someimplementations, the preview renderer may be executed, for example, by auser interface system 201. In some implementations, a preview renderermay operate substantially similar to a visual editor renderer. Forexample, a preview renderer may accept a document object model as input(e.g., a document object model representing a current state of an emailmessage being edited by the visual editor) and output at least a portionof a user interface (e.g., a webpage) based on the input document objectmodel. In some implementations the renderer may be configure to generatea preview representation in which any links within the document are notactive, in which JavaScript and/or other programming elements thatprovide content and layout customization features in a visual editor arenot active, and in which data driven elements are not merged with datasources.

Because, in some implementations, user interface system 201 trackscontent and layout customizations to an email message being customizedby maintaining a representation of a current document object model, asdescribed above, user interface system 201 may generate a preview of acustom email message without querying a database table for informationregarding the custom email message. By limiting such database queries,generation of a preview representation of a custom email message may beperformed at higher speeds. Furthermore, a user (e.g., user computer203) does not need to transmit a representation of a current documentobject model to such a server, so bandwidth used in a preview generationoperation may be minimized.

In some implementations, the preview interface may include a previewcontrol panel 2201. As shown in FIG. 22, in some implementations,preview control panel 2201 may include controls to transmit test letterto one or more desired email addresses. Such test letters may give auser and any desired other recipients another view of the final outputof an email design (e.g., a view from an email client rather than awebpage).

In some implementations, a user may exit a preview mode by selecting anexit preview mode control. A user, for example, may be returned toeditor interface 600 such as the interface shown in FIG. 6 afterselecting an exit preview mode control.

In addition to the customization and preview functionality describedabove, some embodiments, a control panel 619 of a visual interface mayinclude a style sheet editing control (not shown). In someimplementations, a user may select the style sheet editing control toaccess a style sheet editing interface through which a user may editcascading style sheet code of an email message being edited. FIG. 23shows an example of a style sheet editing interface through which a usercan edit cascading style sheet code defining style sheet classes of theemail message displayed in FIG. 6. For example, a user may edit color,font family, text description, and font size elements of the quick linksstyle sheet class through the example interface of FIG. 23.

In some implementations, a user may finished editing the cascading stylesheet code of an email message by selecting either a cancel control toreturn the style sheet code to its preedited state, or a save control tosave the style sheet code edits and return to editor interface 600 inwhich the code edits are incorporated. In some implementations, a usermay also access a preview mode by selecting a preview control to displaya preview representation of an email message including edited stylesheet code.

In some implementations, saving edited style sheet code may include aserver level process. In some implementations, for example, when a userselects a save control and/or a preview control, an updatedrepresentation of the style sheet code may be transmitted to and trackedby user interface system 201. In some implementations, user interfacesystem 201 may update a stored representation of a DOM based on theupdated representation of the style sheet code of the email messagebeing editing.

In some embodiments, a control panel 619 of editor interface 600 mayalso include an edit text letter control (not shown). In someimplementations, a user may select on an edit text letter control toaccess a text letter editing interface. FIG. 24 shows an example textletter editing interface. Through such a text letter editing interface,a user may edit a text version of an HTML email message being edited bythrough editor interface 600. For example, the message being edited byeditor interface 600 may include HTML elements that may not be viewablethrough certain email clients, and/or certain recipients may prefer toreceive a text only version of an email message rather than an HTMLversion. Such preference may, in some implementations be stored in arecipient list similar to traditional data driven elements. A textletter editing interface may provide a user with the ability toseparately edit a text version of an email rather than tying a textversion of an email message directly to an HTML version of an emailmessage.

As shown in FIG. 24, a user may type into an editing pane of a textletter editing interface to change (e.g., add, delete) content of a textversion of an email message. As shown, in some implementations, a textversion of an email message displayed through the text editing interfacemay be based on an HTML version of an email message edited througheditor interface 600. For example, as shown in FIG. 24, the text versionof an email message display in the edit text letter interface includescontent (e.g., text) and a layout (e.g., order of content) of the HTMLemail message displayed in editor interface 600.

In some implementations, the representation of a text letter version ofthe custom email message may be generated by an edit text letterrenderer. In some implementations, the edit text letter renderer may beexecuted, for example, by user interface system 201. In someimplementations, an edit text letter renderer may operate substantiallysimilar to a visual editor renderer and/or a preview renderer. Forexample, an edit text letter renderer may accept a document object modelas input (e.g., a document object model representing a current state ofa email message being edited through editor interface 600) and output atleast a portion of a user interface (e.g., a webpage) based on the inputdocument object model. In some implementations the edit text letterrenderer may be configure to generate an editable text version of anHTML email message being edited through editor interface 600.

In some implementations, a user may finished editing the text letterversion of an email message by selecting either a cancel control toreturn the text version to its preedited state, or a save control tosave the text version and return to editor interface 600 in which theHTML version of the email message is displayed. In some implementations,a user may also access a preview mode by selecting a preview control todisplay a preview representation of a text letter version of an emailmessage. Such preview functionality may be substantially similar topreview of an HTML version of an email message, as described above.

In some embodiments, editor interface 600 may provide functionality toedit an email message for a particular device/display or device/displaytype. For example, a user may edit an email message for display on acellular telephone, personal digital assistant, televisions, billboards,and/or any other mobile or stationary device. Because such devices ordisplay types format displayed information in a unique way, a user maydesire to specially edit an email message to appear properly on thedisplay or device type. Such functionality may be enabled substantiallysimilarly to the edit text letter functionality described above. Suchfunctionality may utilize a device or display specific renderer asdescribed below.

In some embodiments, editor interface 600 may provide functionality toedit an email message for other formats than a text format in additionor as an alternative to the edit text letter functionality describedabove. For example, some implementations may allow a user to edit anemail to be transmitted specifically in Word, PDF, SMS, MMS, and/or anyother desired format. Similar to display and device types describedabove, different formats may result in different display output, so auser may desire to specifically design an email message being sent in aparticular format.

In some embodiment, a visual editor may provide functionality to edit anemail message for a particular email client or other computer program.For example, in some implementations, a visual editor may allow a userto edit an email to be read through a web-based email client differentlyfrom a stand alone email client. Similar to display and device typesdescribed above, different computer programs may display emaildifferently, so a user may desire to specifically design an emailmessage being sent in a particular computer program.

In some embodiments, a control panel 619 of editor interface 600 mayfurther include an anti-spam control. In some implementations, a usermay access an anti-spam interface by selecting an anti-spam control.FIG. 25 shows an example anti-spam interface according to oneimplementation of the instant invention. As shown in FIG. 25, ananti-spam interface may display a spam ranking that indicates a chancethat an email message may be blocked by a spam filter (e.g., a spamfilter of ISP mail server 205F).

Anti-spam functionality may include communicating a representation of acurrently edited email message to a remote server (e.g., user interfacesystem 201). In some implementations, the remote server may process therepresentation of the current email message according to one or moreanti-spam algorithms. For example, in some implementations, an anti-spamalgorithm may count a number of repeated word, count a number of extralong word, count an amount of punctuation, count a number of flaggedwords, determine an amount of an email message constructed from obscuredHTML, and/or determined any other characteristic of an email message.Based on such a determined characteristic, an anti-spam algorithm mayassign an anti-spam score that indicates the chance the message may beblocked by a spam filter. In some implementations, an algorithm mayassign such a score based on observed spam filtering, based oninformation received from one or more spam filter providers (e.g., ISP'scommercial software developers), and/or based on any other criteria.

In some implementations, an anti-spam check may be performed using atracked representation of an email message in memory of user interfaceserver 201. By using such information to perform an anti-spam check, theanti-spam check may be performed more quickly than if a database querywere performed to retrieve a stored representation of an email messagefrom a database server (e.g., 205C).

In some embodiments of a visual editor, in addition to the describedfunctionality above, a user may also add pre-authored content to anemail message being edited through editor interface 600. In someimplementations, a user may select preauthored content from a library ofsuch content. For example, the library of pre-authored content may, insome implementations, include a generic block (e.g., an article block,an introduction block) with written content that may be applicable to avariety of email messages. In some implementations, a library ofpre-authored content may be specific to a particular chosen templatedocument (e.g., a template designer may generate a set of generic blocksthat may be relevant to email messages created using a designedtemplate). In some implementations, a library of pre-authored contentmay be specific to a particular user (e.g., a user may save apre-authored block to the library similar to an image and access thepre-authored block in future email messages). In some implementations, auser may access such a library of pre-authored content through controlpanel 619 of editor interface 600.

In some embodiments, when a user finishes customization of an emailmessage, either temporarily (such as to take a break) or permanently(such as to transmit a finished version), a user may select a globalsave control to perform a database level save of an email message. Forexample, when a user selects a global save control, a request may betransmitted from a user (e.g., user computer 203) to user interfacesystem 201. In some implementations, the server may save arepresentation of a remotely stored document object model correspondingto an email message being edited through editor interface 600 to adatabase table (e.g., a database maintained by database server 205C).

In some embodiments, if a user finishes customizing an email message,the user may select on a save and continue control to both save thecurrent email message and continue to a transmission interface.

Returning to process 300 shown in FIG. 3, after a user has been providedwith an editor interface (e.g., 600) at block 307 and completescustomizing an email message, as indicated at block 309, process 300 mayinclude processing and transmitting a custom email message.

In some embodiments, processing a custom email message may includeselecting one or more recipients of the email message. FIG. 26 shows anexample interface through which a user may select one or more predefinedrecipient lists. A user for example may select check box 2601 to selectthe associated recipient list and the select next to indicatetransmission to that recipient list is desired.

In some embodiments, a user may create and/or alter recipient listsbefore or after customizing an email message. For example, FIG. 27 showsan example recipient list management interface. As shown, the exampleuser has two recipient lists, a general interest list and a premiumlist. The user may select to generate additional lists, select anexisting list to edit, delete an existing list and/or merge one or moreexisting lists through a list control panel 2701. FIG. 28 shows anexample interface that may be used in some implementations to create anew recipient list. A user, for example, may use such an interface toimport a file containing an email recipient list (e.g., a delimitatedtext file, an exported email list from an email client) and/or access anentry interface through which the user may type email addressesdirectly.

FIG. 29 shows an example entry interface that may be used in someimplementations to allow a user to generate a recipient list. Throughthe example interface of FIG. 29, a user may enter recipient emailaddress information by entering such information into an email addresscolumn 2901. A user may select a plurality of data driven elements to bestored for each recipient through drop down boxes 2903 and enterassociated information in data driven columns 2905. Although the exampleinterface includes four data driven columns, other implementations mayinclude any number of data driven columns and/or an interface to add ordelete such columns.

In some implementations, after selecting one or more recipients, acustom email message may be transmitted to the selected recipients. Insome implementations, after selecting one or more recipients, a user mayaccess an email status interface to schedule future transmission of anemail message, immediate transmission of an email message, or save anemail message as a draft. FIG. 30 shows an example status interface.After selecting a desired transmission action a user may select a finishcontrol to schedule transmission, transmit an email message, or save thecampaign as a draft. A user, in some implementations, may log on to asystem (e.g., using a user name and password) to access such a statusinterface to change or create a transmission schedule.

In some embodiments, transmission of email messages to recipients (e.g.,at a scheduled time) may include generating a plurality ofrepresentations of a custom email message. For example, in someimplementations, a renderer (e.g., a preview renderer) or other mailgenerating process may be executed by a server (e.g., a mail farmserver) to generate a representation of a custom email message having adesired content and layout without editing elements such as those thatare visible through an editor interface (e.g., similar to a previewrepresentation as described above). In some implementations, a previewrenderer may be used to generate such an email message. In someimplementations, the mail renderer or a separate renderer process maygenerate text letter representations for users desiring text onlyrepresentations of a custom email message. In some implementations, suchtext letter representations may be similar to the edit text letterrepresentations described above without editing functionality.

In some implementations, a preview renderer or a separate merge processmay be configured to complete data driven elements in a custom emailmessage be entering appropriate information from a recipient list storedin a database table (e.g., on database server 205C) to generate aplurality of final email messages that may then be transmitted to eachrespective desired recipient.

After transmitting email messages, process 300 may end at block 311.

Renderers

In some embodiments, various representations of email messages may begenerated by one or more renderers executed on one or more servers. Insome implementations, such renderers may be substantially modular. Forexample, in some implementations each renderer may accept asubstantially or exactly similar input (e.g., a representation of adocument object model). Each renderer may output a differentrepresentation of an email message depending on the purpose of therespective renderer and/or other renderer parameters. Such modularityallows a single representation of an email message to be used as inputto generate a plurality of different output representations, rather thanrequiring multiple representations of a single email message to bemaintained.

For example, a preview renderer may generate a preview representation ofan email message (text and/or HTML depending on render parameters), testletter sent through a preview interface, and live output representationsof an email message, an edit text letter renderer may generate an edittext letter representation of an email message, and a visual editorrenderer may generate a visual editor representation of an email. Anappropriate renderer may be selected based on a received indication fromthe user (e.g., request for a preview, a request to transmit a liveletter, a request to access the editor interface, etc.).

In some implementations, the visual editor render may insert a pluralityof JavaScript hooks into an HTML document (e.g., associated with titlebars, buttons, etc.) representing an email message. In someimplementation, this output may include the DOM that user interfacesystem 201 and/or user computer 203 maintains. In some implementations,JavaScript event handlers may be applied to the plurality of hooks. Insome implementations, JavaScript code may also disable all the links andform submission in an email message for certain versions of an emailmessage.

In some implementations, the output for preview, test letters and liveletters (HTML and text) are generated by the preview renderer. Forpreview and text letters, the renderer may add hooks to the links to nottrack when a user selects them. For text letters, the renderer may stripout all the HTML tag and apply text letter rules, such as handling linksand images differently. In some implementations, the output for textletter generated for the edit text letter functionality may be slightlydifferent from the regular text letter (preview, test letter, and liveletter). The output for example may keep the links, greeting andsubscriber data tags so that when the text letter is rendered forpreview, text and live mode, the renderer tracks the links and expandsindividual recipient information.

In one example implementation of a set of three renderers (e.g., visualeditor, preview, and edit text letter renderers), each renderer mayinclude a parser process to parse a representation of a document objectmodel received as input. In one implementation, a standard parser suchas the stAX parser may be used.

With respect to HTML email messages, for a visual editor, preview, testletter and live letters, the renderers may parse out all anchor tags(<a>) and regenerate them by adding custom tracking code that allowstracking of each select a recipient or user makes on each one of thelinks on the email. The renderers may also parse out the image tags(<img>) to make sure to pull the right image from an image library. Insome implementations, if an image is from an image library and has beendeleted from the image library, a renderer may place a place holderimage in its location to indicate that the image that goes on that spothas been deleted.

Further, the renderers may parse out the special tokens where thegreeting and recipient information (e.g., data driven elements) isplaced. In some implementations, for the greeting tokens, renderers maymake the correct substitution based on the user selection on what theywant to display for the greeting. For example, if using the primarygreeting, the renderer may insert a recipient's information (First Name,Last Name, First & Last Name, etc.). If the recipient's information isnot available, the renderer may default back to the secondary greeting.In some implementations, for the recipient information substitution, ablind substitution may be performed (i.e., if the specific recipient'sinfo is unavailable, display a blank value). In some implementations,for visual editor and preview representations the renderers may insertthe user's (i.e., the person editing the email message) information ingreeting and other data driven locations.

Furthermore, the renderers may add a permission reminder to the top ofthe email if the user has checked off to add permission reminder to theemail. The renderers may also add footer information to the bottom ofthe email. Even though in some implementations a user may not be able tofully edit all content of a footer, there may be certain things the usercan edit and a renderer may need to determine. For example, a user canspecify the language for the footer, a user can specify whether toadd/remove an update profile sentence from the footer, user can requesta footer not containing a logo, a user can request an entirelycustomized footer With respect to preview, test and live HTML messages,the renders may further convert all style sheet classes into inlinestyle tags, similar to converting styles into edit mode of a block asdescribed above. In some implementations, because some email clients donot support inline style, to preserve some of the look and feel of anemail message, the renderers may convert some of the style into regularHTML attributes like font styles, background color and image and bordercolor.

For example, in some implementations, in the case of background colorand image and border color, the renderers may add the respectiveattributes to the tag that has the reference to the style class, i.e.,bgcolor, background, and border-color. For example a table using a stylesheet defined as:

.myclass{ background-color: #ff0000; background-image:url(http://some.image.here); border-color: #0000ff; }may be converted into a table defined as:

<table style=“background-color: #ff0000; background-image:url(http://some.image.here); border-color:#0000ff;”bgcolor=“#ff0000” background=“http://some.image.here”border-color=“#0000ff”></table>

As another example, in some implementations, for font styles, therenderers may add a <font> tag after the tag that makes references tothe style class. Also, in some implementations, font-size may beconverted into an absolute font size value. For example for a spanelement using a style class defined as

.myclass{ font-family: verdana; font-size: 10pt; color: #000000; }may be converted into:

<span style=“font-family:verdana;font-size:10pt;color:#000000;”><fontface=“verdana” size=“2” color=“#000000”></font></span>.

With respect to live letters only, the renderers may add an opentracking element to some email messages that determines if a recipientopens an email message and/or selects one or more links within an emailmessage and transmits an indication of such tracking to a remote server(e.g., open/click tracking server 205J). With respect to preview andtest letters only, the renderers may add a flag to all links indicatingthat tracking of the links or opening of the email should not occur.

With respect to text versions of an email message, the renderers mayperform different function than with respect to HTML versions of anemail message.

For example, with respect to preview, test letters, live letters andedit text letter mode the renders may strip out all the tags. In someimplementations, the renderers keep track of the number of line breaksneeded to be added based on the tags (e.g., convert a <p> into 2 linebreaks). In some implementations, if more that one tag appearsconsecutively before any text, the renders may use the tag correspondingto the largest line break to track the line breaks needed. For example,in the content:

<p> <div>Hello World</div> </p>the <p> tag may resolve to two line breaks and the <div> tag may resolveto one. In this case, the renderers may honor the tag with the largestnumber of line breaks and ignore the other one resulting in two linebreaks before the “Hello World” text rather than three.

In some implementations, the renderers may insert line breaks so thattext may wrap correctly. For example, a line break may be added after apredetermined number of characters. In one implementation, thepredetermined number of characters may include approximately eightycharacters so that text does not run passed a standard display screen'sdisplay limitations.

In some implementations, the renderers may add a permission reminder tothe top of the email if the user has checked off to add permissionreminder to the email. And, in some implementations, the renderers mayadd the footer information to the bottom of the email.

In some implementations, for <img> tags, if the <img> is wrapped by an<a> tag and the <img> tag has a non-empty alt attribute, the renderersmay treat the <img> tag as a text link using the value from the altattribute. If the <img> tag has no alt attribute or no <a> tag wraps the<img> tag, the renderers may remove the image completely.

With respect to preview, test, and live letters only, the renderers mayfurther construct text version links for the email message. For example,for <a> tags including a valid href attribute, the renderers may savethat value use the href value to construct a link text based on the nextappearing text element. For example, the code:

<a href=“http://some.where.on.the.web”>click here</a>

may be converted into:

click here [http:://our.tracking.bug?http://some.where.on.the.web].

In some implementations, the renderers may also parse special tokenswhere greeting and recipient information may be located. In someimplementations, for the greeting tokens, renderers may make the correctsubstitution based on the user selection on what they want to displayfor the greeting. For example, if using the primary greeting, therenderer may insert a recipient's information (First Name, Last Name,First & Last Name, etc.). If the recipient's information is notavailable, the renderer may default back to the secondary greeting. Insome implementations, for the recipient information substitution, ablind substitution may be performed (i.e., if the specific recipient'sinfo is unavailable, display a blank value). In some implementations,for preview representations the renderers may insert the user'sinformation in greeting and other data driven locations.

With respect to live letters only, the renderers may further add an opentracking element to some email messages that determines if a recipientopens an email message and/or selects one or more links within an emailmessage and transmits an indication of such tracking to a remote server(e.g., open/click tracking server 205J). With respect to preview andtest letters only, the renderers may add a flag to all links indicatingthat tracking of the links or opening of the email should not occur.

With respect to edit text letter mode, the renderers may leave <a> alonerather than replace them as in other modes. In some implementations,special tokens such as greeting and recipient data driven elements maybe left alone in this mode.

Although the above description of process 300 and the example rendererdescriptions include three renderers (i.e., preview, visual editor, andedit text letter), it should be understood that any desired renderersmay be used in other embodiments of the instant invention. Moreover, itshould be understood that a single process or no process at all mayperform the functions of a renderer process in still other embodimentsof the instant invention.

In some embodiments, for example, one or more renderers may beconfigured to generate representations of an email message designed fora particular device or display type. In some implementations, the abovedescribed preview, visual editor, and/or edit text letter renderers maybe configured with such functionality by inputting a device parameterinto the renderers in addition to a representation of a DOM. In someimplementations, rather than the above described preview, visual editor,and edit text letter renderers, alternative and/or additional renderersmay be configured with such functionality (e.g., device specificrenderers).

In some embodiments, for example, a renderer may generate arepresentation of an email message that is designed to be delivered to arecipient using a particular device type and/or edited through aparticular device type. For example, in some implementations, a renderermay generate a representation of an email message that is designed to beedited (e.g., through a visual editor) on one or more of a cellulartelephone, a personal digital assistant, and/or any other device (mobileor stationary). Such a representation may be designed specifically forthe device type so that functionality and/or usability may be optimizedfor the device type. For example, because some portable devices havesmaller display screens than stationary device, an editor interfacerenderer for a portable device may optimize a format of an emailrepresentation for portable devices (e.g., cellular telephones) byminimizing certain control interfaces that would be larger for a visualeditor optimized for a stationary device (e.g., desktop computers)and/or adjusting a number of characters displayed per line to fit adisplay size.

As another example, some device or display types may support a differentset of programming formats (e.g., HTML) or programming languages (e.g.,JavaScript). A render may be configured to optimize a representation ofan email message to be displayed using the supported set of programmingformats and/or functions. For example, in some implementations, stylesheet classes may be unsupported and may be replaced with inline class,certain JavaScript or other programming function may be unsupported andmay be replaced with other supported elements, and/or HTML may not besupported at all and may be replaced with another programming format(e.g., SMS, MMS, a proprietary input, etc.).

In some implementations, a renderer may generate a representation of anemail message that is designed to be viewed by a recipient using one ormore particular device or display type (e.g., cellular telephone,personal digital assistant, televisions, billboards, and/or any othermobile or stationary device), programs (e.g., web-based email client) orformats (e.g., Word, text, HTML). Such a representation may be optimizedfor display on the particular device or display type, program, orformat. As described above with respect to optimizing for editing on aparticular device type, optimizing for viewing on a particular devicetype, program or in a particular format may include changing format,programming, and/or any other elements of a representation may beoptimized for such display.

In some embodiments, renderers may be configured to provide specialediting functionality for specific target devices, formats, and/orprograms. An example of such a renderer, the edit text renderer, isdiscussed above. In some implementations, other such renderers maygenerate a representation of an email message that may be edited togenerate email versions particular to other formats than text (such asWord, PDF, etc), particular to target devices (such as mobile devices),and/or particular to target programs (such as web-based email clients).Such renderers may function substantially similar to the edit textrenderer described above with configuration to generate an editableversion of an email for a particular format, device, and/or targetprogram rather than text.

Having thus described several aspects of at least one embodiment of thisinvention, it is to be appreciated various alterations, modifications,and improvements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis disclosure, and are intended to be within the scope of instantinvention. Accordingly, the foregoing description and drawings are byway of example only.

1.-53. (canceled)
 54. A computer-implemented method for generating atleast one custom email message based, at least in part, on input from auser of a computer system, the computer system having a display, themethod comprising acts of: A) receiving from the user an indication of adesired version of the custom email message; B) selecting an emailrenderer based, at least in part, on the indication of the desiredversion of the custom email message; C) rendering the desired version ofthe custom email message using the selected email renderer; and D)presenting, to the user in the display of the computer system, thedesired version of the custom email message.
 55. The method of claim 54,wherein the selected renderer includes at least one of a previewrenderer, an editor renderer, and an edit text letter renderer.
 56. Themethod of claim 54, wherein the desired version includes a previewversion and the selected renderer includes a preview renderer.
 57. Themethod of claim 56, wherein the act C includes generating a hypertextmarkup language representation of the custom email message based, atleast in part, on a document object model representation of the customemail message.
 58. The method of claim 56, wherein the act C includesgenerating a text representation of the custom email message based, atleast in part, on a document object model representation of the customemail message.
 59. The method of claim 56, wherein the previewrepresentation includes an approximation of the custom email message asthe custom email message may appear to a recipient of the custom emailmessage.
 60. The method of claim 56, wherein the desired versionincludes a preview for at least one of a device type, a format, and aprogram, and the act C includes generating a preview representation ofthe customized email message designed for the at least one of the devicetype, the format, and the program based, at least in part, on a documentobject model representation of the custom email message.
 61. The methodof claim 54, wherein the desired version includes an editor version andthe selected renderer includes an editor renderer.
 62. The method ofclaim 61, wherein the act C includes generating a hypertext markuplanguage representation of the custom email message based, at least inpart, on a document object model representation of the custom emailmessage.
 63. The method of claim 61, wherein the editor version includesa plurality of JavaScript hooks that enable at least one customizationof at least one of a content of at least one of the plurality of contentblocks and a layout of the plurality of content blocks to be entered bythe user through an editor interface.
 64. The method of claim 63,further comprising an act of E) presenting, to the user in the displayof the computer system, the editor interface displaying the editorversion.
 65. The method of claim 63, wherein the desired versionincludes an editor for a device type, and the act C includes generatingan editor representation of the customized email message designed forthe device type based, at least in part, on a document object modelrepresentation of the custom email message.
 66. The method of claim 54,wherein the desired version includes an edit text version and theselected renderer includes an edit text renderer.
 67. The method ofclaim 66, wherein the act C includes generating a text representation ofthe custom email message based, at least in part, on a document objectmodel representation of the custom email message.
 68. The method ofclaim 66, wherein the edit text version is formatted to enable editingthrough an edit text interface.
 69. The method of claim 68, furthercomprising an act of E) presenting, to the user in the display of thecomputer system, the edit text interface displaying the edit textversion.
 70. The method of claim 54, wherein the desired versionincludes an editable version for at least one of a device type, aformat, and a program, and the selected renderer includes an editrenderer for the respective at least one of the device type, the format,and the program.
 71. The method of claim 70, wherein the act C includesgenerating a respective edit representation of the custom email messagebased, at least in part, on a document object model representation ofthe custom email message.
 73. The method of claim 70, wherein therespective edit version is formatted to enable editing through an editinterface.
 74. The method of claim 72, further comprising an act of E)presenting, to the user in the display of the computer system, the editinterface displaying the edit text version.
 75. The method of claim 54,wherein the desired version includes a live version and the selectedrenderer includes a preview renderer.
 76. The method of claim 74,wherein the act C includes generating a hypertext markup languagerepresentation of the custom email message based, at least in part, on adocument object model representation of the custom email message. 77.The method of claim 74, wherein the act C includes generating a textrepresentation of the custom email message based, at least in part, on adocument object model representation of the custom email message. 78.The method of claim 74, wherein the act C includes inserting at least ondata driven element into the live version.
 79. The method of claim 74,further comprising an act of E) transmitting the live version to atleast one recipient.
 80. The method of claim 74, wherein the desiredversion includes a live version for at least one of a device type, aformat, and a program, and the act C includes generating a liverepresentation of the customized email message designed for therespective at least one of the device type, the format, and the programbased, at least in part, on a document object model representation ofthe custom email message.
 81. The method of claim 54, further comprisingan acts of: E) rendering a live version of the custom email messageusing a live renderer; and F) transmitting the live version to at leastone recipient.
 82. The method of claim 80, wherein the act E includesrendering the live version for a desired device type.
 83. The method ofclaim 82, wherein the live renderer includes a device specific liverenderer.
 84. The method of claim 82, wherein the live renderer includesa generic live renderer usable for a plurality of devices types.
 85. Themethod of claim 54, wherein the selected renderer includes at least oneof a device type renderer, a format type renderer, and a program typerenderer.
 86. The method of claim 85, wherein the at least one devicetype includes at least one of a cellular telephone, a general purposecomputer, a personal digital assistant, a television, and a billboard.87. The method of claim 85, wherein the desired version respectivelyincludes at least one of a version designed for the device type, aversion designed for the format, and a version designed for the program.